Should we rename the MASTER forest?
Dmitri.Trembovetski at Sun.COM
Thu Nov 8 15:41:32 PST 2007
Peter B. Kessler wrote:
> The VM team (the hotspot/ subdirectory) has tended to work the other
> way: we have a repository we are all working on and when we get near
> a release we make a clone of that and call it HotSpot-N. But the
> main repository keeps moving towards HotSpot-N+1.
> That means that bug fixes that are needed in HotSpot-N have to be
> forward-ported to the main repository. Or, more likely, fixed in
> the main repository and patched back to HotSpot-N. I think the need
> to fix things in two places will always be with us, no matter which
> way we clone the repositories.
Java2D team works the same way. Our team workspace never
changed, we just forked off branches for specific releases
or milestones (beta, beta2, rc) when needed, and reparented
it when a new master workspace for the next release
Which was pretty neat since we have full history of
putbacks into our team workspace (in Teamware the history
of _the workspace_ doesn't propagate with putbacks, only
Of course this is less of an advantage with Hg.
More information about the discuss