Re: [Axiom-developer] sourceforge/silver

[root]

> Here is how I see the situation:
> 
>             |       |            |           |
>             |       |        darcs and       |
>             |    next big =  hg mirrors      |
>             |    experiment      |           |
>  gold       |   /                            |
>  gold <---- |  /                             |
>  (52)     silver  (SourceForge) <=====> Google Code
>             |                             mirror
>             |\___merge___                    |
>  gold <---- |            \        |          |
>  (51)       |\__          |       |          |
>            /    \   back  |   darcs and      |
>  gold <---|-<----\ .....> / = hg mirrors     |
>  (50)     /      /  port |        |          |
>          |      |        |        |          |
> Now:   silver trunk    build
>          |      |   improvements
>         tla     |    /
>                 |   /
>                 |  /
>  gold <------ trunk
>  (49)           |
>                CVS
> 
> 
> What Gaby is talking about is shown as ....> above.


Well, Bill, I nominate you for ascii artist of the year!
unfortunately i'm too left-brained to figure out what you mean.

are you trying to say that silver patches get backported into branches?

that's fine. i'm just concerned that at some point Gaby asserts that
"it's done" and i have a HUGE pile of completely unrelated changes
dropped on my desk. each change is going to be debated (count on it,
given this crowd :-) ), its going to take forever (translation: more
than a week :-) ), and the claims will be "well, it works so what's
the problem" over every objection. the fact that it works is a
necessary but not sufficient condition. 

i'm trying to minimize the pain by asserting that this particular
branch has a stated goal, that of making axiom use autotools.
anything that depends on that should be done in that branch.
changes which do NOT depend on that should be done against silver
or gold and Gaby can pick them up at will.

t