JDK 7 moving to mercurial -- svn repositories

Kelly O'Hair Kelly.Ohair at Sun.COM
Sun Oct 21 20:32:16 UTC 2007

The official Mercurial repositories will have NO history from
the TeamWare workspaces or SubVersion repositories, they will
be fresh repositories starting with the promotion of Build 23.

Importing history from one SCM to another is an inexact science
and we want accurate Mercurial repository history.

With Mercurial, the working set files can easily be displaced with a
different source tree if you wanted to see the differences between past
promotions and the current state of a repository.


Mark Wielaard wrote:
> Hi Xiomara,
> On Tue, 2007-10-09 at 12:57 -0700, Xiomara.Jayasena at Sun.COM wrote:
>> Stephen J. McConnell wrote: 
>>> On Tue, 2007-10-09 at 14:17 +0200, Dalibor Topic wrote:
>>>> Xiomara.Jayasena at Sun.COM wrote:
>>>>> As many of you know the jdk 7 workspaces will be moving from
>>>>> Teamware to
>>>>> Mercurial.  As of now we host svn repositories here:
>>>>> https://openjdk.dev.java.net/source/browse/openjdk/jdk/trunk/
>>>>> and
>>>>> here:
>>>>> https://jdk-jrl-sources.dev.java.net/svn/jdk-jrl-sources/jdk7/trunk/
>>>>> Once JDK 7 moves to Mercurial we would like to know whether
>>>>> there is a
>>>>> need to keep the svn repositories out there and if so forever?
>>>>> overlap
>>>>> for sometime?  I am trying to figure out what would be best for
>>>>> most
>>>>> people.
>>>> I don't think there is a need to keep them around, as you have the
>>>> zip-ed/tar-ed source code downloads for people just wanting to
>>>> fetch and
>>>> build the 'latest' build, while a source code repository, for me
>>>> at
>>>> least, is the place where the actual work is happening.
>>>> And there can be only one of those. ;)    
>>> I agree completely.
>>> Backups of legacy to take care of the past and move on to Mercurial
>>> for
>>> the future.
>> Thank you for your feeback -- these responses along with others I have
>> received seem to be in the same line of thought.  So it is OK to do
>> away with the svn repositories once the Mercurial ones are up.
> Yes I think so. If the old history is imported into mercurial I don't
> see any reason to keep the svn repos around. There is also a mercurial
> mirror of the svn repositories, with all changesets already at
> http://icedtea.classpath.org/hg/openjdk/ This can be kept around for
> people who want to view the history also. I personally found that
> mercurial mirror handy to easy figure out when what changed between
> source drops (since with mercurial as opposed to subversion you don't
> need any network connection which greatly slows things down for doing
> quick changeset searches).
> Cheers,
> Mark

More information about the discuss mailing list