Should we rename the MASTER forest?

[David Herron]

Roman Kennke wrote:
> Hi David,
>
> Am Donnerstag, den 08.11.2007, 12:23 -0800 schrieb David Herron:
>   
>> Roman Kennke wrote: 
>>     
>>> Hi Mark,
>>>       
>>>> Given all this I hereby propose that we rename the MASTER forest
>>>> simply to "jdk7".    
>>>>         
>>> One thing I don't understand is, why is something in the repository URL
>>> named with a release (-like) number? Is the repository only made for
>>> JDK7, and we start a fresh one for JDK8? Doesn't seem to make much sense
>>> to me. Why not simply drop the '7' and name it 'jdk'? My personal
>>> favorite is 'openjdk' though. IMO the URLs should read like:
>>>
>>> http://hg.openjdk.java.net/openjdk/<sub-repo>
>>>
>>> /Roman 
>>>       
>> I'm thinking a similar thing.
>>
>> But, the team practices Mark alluded to also includes having a new
>> MASTER for each release.  There's the MASTER for 1.4, for 1.5, for 6,
>> and for 7 and so on.  I think that would mean over time the URL's
>> would read
>>
>> http://hg.openjdk.java.net/openjdk7
>> http://hg.openjdk.java.net/openjdk8
>> http://hg.openjdk.java.net/openjdk9
>> ...
>>     
> So, if I understand it correctly, you are 'branching' at the beginning
> of a release cycle, instead after the release. And when a new release
> cycle starts, you would clone jdkX to jdkX+1 ? Strange practice for my
> taste...
>
> /Roman
This way the workspace contains the history of changes for the given 
release cycle.

At the end of a release there's a clone created that's the beginning of 
the next release.  So it's a matter of perspective whether the clone is 
at the "end" or "start" of a release.

This practice comes partly from the features of TeamWare in that it 
supports multiple independent workspaces.  It's common practice to clone 
workspaces to do work.

This is different in many ways from SCM systems that use a central 
repository like CVS does.  Where in CVS you would tag the repository at 
a given release, and then do per-release work in a branch... this is 
where we instead use multiple repositories.  Speaking for myself I've 
found branches and tags in CVS to be confusing, despite having used CVS 
of and on for 15 yrs, but multiple repositories in TeamWare is very 
straightforward. 

- David Herron

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/discuss/attachments/20071108/16e39ec3/attachment.html>