Mercurial repo for openjdk6 drops
Joseph D. Darcy
Joe.Darcy at Sun.COM
Mon Sep 22 13:40:02 PDT 2008
Joseph D. Darcy wrote:
> Kelly O'Hair wrote:
>> Speaking from experience, any attempts at cleanly creating changesets
>> from TeamWare data alone is a waste of time. Just doesn't work well.
>> Granted we have pretty complete OpenJDK6 changeset data (data beyond
>> the TeamWare data) and could potentially do this, it's quite a bit of
>> grunt work to accomplish. Before we go off on this kind of adventure
>> we need to make sure the time spent is worth it.
>> A different approach would be to create changesets per build/promotion,
>> but those kind of large changesets can have limited usefulness.
>> I'll try and talk to Joe about this tomorrow.
>> Also, don't forget that the OpenJDK7 sources are a Mercurial forest,
>> not just one repository. I assume that we want to mimic the same
>> forest layout, keeping the langtools, corba, jaxp, jaxws, and hotspot
>> sources in their own repositories, separate from the core 'jdk'
>> That allows us to do some plug and play with these repositories
>> between OpenJDK6 and OpenJDK7.
> Yes, my thinking has been to mirror the overall JDK 7 repository
> forest structure in OpenJDK 6.
Quick follow-up, I've been traveling recently and haven't had a chance
to chat with Kelly yet.
Given that there is currently the per-build external Mercurial
repository and that it is easy to get the list of bugs fixed in a build,
retroactively synthesizing the (approximate) patches associated with a
set of bugs *might* be workable since figuring out the bug <-> file
mapping shouldn't be that bad. If those interested in seeing the past
history synthesized these patches, I could focus on finishing getting
the OpenJDK build 12++ code ready for Mercurial and then reverse apply
the set of patches to get back to the earlier public source drops.
However, this might be more work than I think and I'll want to talk to
Kelly about the detailed logistics of what would be necessary for this
My priority is on getting the "official" Mercurial repository up and
running so we can collaborate there going forward as opposed to spending
lots of time on retrofitting the existing build history into the new
Also, in the future I'd like to consider an infrastructure where areas
like corba, jaxp, and jaxws for OpenJDK 6 could be managed as patches to
an imported code base rather than having a fully populated copy of the
code under revision management for the release.
More information about the distro-pkg-dev