Should we rename the MASTER forest?

[Neal Gafter]

On Nov 8, 2007 1:54 PM, Mark Reinhold <mr at sun.com> wrote:

> Our usual practice has been to freeze the master TeamWare workspaces for
> each release when that release goes final.  Successor releases, whether
> they're small update releases or the next big feature release, are
> developed in their own workspaces, which start out as clones of the
> original master.  This is, yes, different from the way that people tend
> to use centralized SCMs such as CVS and Subversion.
>
> Transposing this to Mercurial: When JDK 7 ships then the jdk7 master
> forest will be archived, and work on JDK 8 will begin in a jdk8 forest,
> which will initially be a clone of jdk7.


One problem with this approach is that work on the next release cannot begin
until the powers that control these workspaces are ready for work to begin
on the next major release. Within Sun, that has resulted in engineers being
unable to make significant changes for the following release until some time
after the current release is completed. This is particularly painful during
the final ramp-down months of a release, when only critical changes are
accepted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/discuss/attachments/20071108/5ba68d85/attachment.html>