JDK 7 moving to mercurial -- svn repositories

Kelly O'Hair Kelly.Ohair at Sun.COM
Mon Oct 29 20:44:24 UTC 2007

But the granularity of the change history is incomplete between the
OpenJDK subversion and icedtea mercurial repositories.
All information about who made a change or why the change was made
has been lost in the subversion repository, all you have are all the changes
made between promotions, all munged together with no changesets for bug
fixes or feature additions.

Accurate SCM changesets should record the correct date/time the changeset
was created, and by who, and include the specific comments added by the
engineer making the change. This is difficult to get right when transitioning
history between SCM's.


Mark Wielaard wrote:
> Hi Kelly,
> On Sun, 2007-10-21 at 13:32 -0700, Kelly O'Hair wrote:
>> Mark Wielaard wrote:
>>> 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).
>> 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.
> It isn't that hard. Moving out of CVS is not nice. But most other SCMs
> are pretty easy to move between. The OpenJDK mercurial repo on
> http://icedtea.classpath.org/hg/ is kept up to date with the subversion
> repo completely automatically without any human intervention for
> example. 
> Cheers,
> Mark

More information about the discuss mailing list