Mercurial repo for openjdk6 drops

[Joseph D. Darcy]

Mark Wielaard wrote:
> Hi,
>
> On Sun, 2008-09-14 at 19:21 -0700, Martin Buchholz wrote:
>   
>> Joe, as I mentioned to you offline,
>> I think having some history for the mercurial repos
>> at creation time would be valuable.
>>
>> I bet the community would do the conversion down to the
>> changeset if Sun provided the history in Teamware form.
>>     
>
> Yes, we were just discussing that again on irc. And Martin is completely
> right. We would be happy to help in any way getting the individual
> patches and changesets into a public mercurial repository if made
> available (at least the back to the future parts, clearly anything from
> before jdk7 will be a bit too hard).
>
> It would greatly help with reviewing the code and any changes in the
> future.
>
> Cheers,
>
> Mark
>   

Hello.

While I'm sympathetic to the request and appreciate the offer of help, 
it is unlikely I'll be able to publish the initial Mercurial 
repositories with any history.  The most history that could be published 
dates back to when OpenJDK 6 branched off from the already open sourced 
JDK 7.  The total amount of bugs fixed from then until now is on the 
order of 400-500, with somewhat fewer logical changesets.  This number 
of changesets is quite small compared to the amount of pre-Mercurial 
history that is not being published externally at all.  However, the 
number is large enough that is would be troublesome for me to reliably 
synthesize changesets.   I don't have Martin's process for scripting and 
SCM hackery and one of the limitation of the teamware SCM is that the 
changes are only really tracked on a per-file basis.  Published 
truncated teamware histories outside of Sun's firewall for people to 
help cons up changesets might be technically possible, but much of the 
prep work and reviews would have to be done internally and the 
costs/benefits on that portion don't look attractive to me.  I'd rather 
see the Mercurial repository up and running sooner so all future changes 
can be tracked well.

-Joe