Mercurial repo for openjdk6 drops

[Mark Wielaard]

Hi Kelly,

On Thu, 2008-09-25 at 14:53 -0700, Kelly O'Hair wrote:
> I'm starting to work on the OpenJDK6 Mercurial conversion. My plan is for
> Build 5 to be the Rev 0 changeset, and I will try and create changesets
> for each of the bug fixes in a Build.

Would it be possible to reconstruct the openjdk7 revision that was the
original starting point for the openjdk6 tree? That would be very
helpful to have for forward and backward porting between the two trees.
If you could make that rev0 and then have one giant changeset to build 5
as rev1 that would be really great.

For example we have found some nasty AWT bugs that have been fixed in
openjdk7, but it was somewhat hard to track down what was needed because
the origin of the awt code in openjdk6 wasn't exactly known.

> So I'll be going through the list of fixes for each build, try and create a
> changeset for it, and at the end I'll copy in the final source for that
> build and see what I missed. The final changeset may be one for the remaining
> bugs fixed. Then I'll tag that changeset and move on to the next build.
> I'm calling this Total Recall, in that I'm essentially doing a replay
> of the Build 5 through Build 12 changes.

Wow. That is really, really great. And it must be a real pain to go
through all that. Thanks a lot for doing this! Hope it will not drive
you mad.

> One of my concerns is that normally we want every changeset fully vetted
> with regards to at least building on all platforms.
> Unfortunately with Teamware, the changes are often not kept in any sequential
> order like the Mercurial changesets, they are independent SCCS file changes.
> The history file can help me, but I'm dealing with a very old DSCM system here.
> 
> So I'll try and re-create the same order the changes were made, and then
> occasionally make sure it builds on all platforms.
> The final sources for each Build we know builds ok on all platforms, those
> are effectively the source bundle drops.
> So I can't guarantee that every changeset is cleanly buildable on all
> platforms.
> Is that acceptable to everyone?

It would certainly be to me. I am already very pleased that you are
attempting to get more than just one changeset per build drop. I think
the data will mostly be used for historical purposes (what was changed
when together with what?). Not for actually building.

Thanks,

Mark