Should we rename the MASTER forest?

[Roman Kennke]

Hi there,

> 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.

Seems like with Mercurial it doesn't really matter that much if we go
the centralized approach of having one trunk from which the release
branches are cloned or if the next development branch is cloned from the
current release. The effect should be the same for all purposes. 


> If the top-level repository is called jdk, then it's weird that
> there's a jdk/jdk subdirectory.  Can we think of a better name for
> that?  jdk/jdk certainly isn't the whole JDK, since it doesn't
> contain the VM, langtools, or the other important bits.  I'd let
> the people that own that code come up with a name for it.

What about 'classlibs' for the class libs, rather than jdk?

/Roman
-- 
Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org
aicas Allerton Interworks Computer Automated Systems GmbH
Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
http://www.aicas.com   * Tel: +49-721-663 968-0
USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe
Geschäftsführer: Dr. James J. Hunt