Re: classpath-0.98 merge for GCC-4.4

2008/8/11 Matthias Klose <[email protected]>:
> Looking forward at the the end of stage1 for GCC-4.4 and an upcoming
> classpath-0.98 release ... Apparently cp won't be released before the end of
> stage1,

According to:

http://gcc.gnu.org/ml/gcc/2008-08/msg00131.html

the closing date for stage 1 is the 31st of August.  I think we should
be able to have a
GNU Classpath 0.98 release by then, hopefully well before then.  I was
nearing the point
of making a release, but had to stop to dedicate more time to the
OpenJDK challenge (my
original hope being that there would be a release much earlier, so
changes to Classpath could
also be part of the challenge project -- clearly this didn't work out).

Matthias, how long would you need between a Classpath release and the
deadline to port
the new version to GCJ? And is there any way I can help with this?

> and GCC going directly from stage1 to stage3 would not allow a merge of
> a new classpath. How should we proceed? Merge cp from the trunk as it is today,
> and then ask for an exception for the merge of the final 0.98 release? Or ask
> for an exception to merge the final cp release during stage3? The merges itself
> should be straight forward.

Ideally, I'd prefer a GCJ release to be based on a Classpath release,
if just so bug
reports against GCJ 4.4 can be more closely linked to a Classpath
release.  That said,
I think the tree is in okay shape at the moment.  If you do merge now,
I'd suggest using
the time to test the completed merge, especially the new locale changes.

As a third option, perhaps the main merge could be done now, covering
all the feature
changes (GJDoc, localisation).  I could then submit the remaining bug
fixes planned for 0.98
to GCJ separately, as they get sent to Classpath.  We'd then end up
with 0.98 in GCJ
(effectively).

>
>  Matthias
>

Thanks for handling this merge,
-- 
Andrew :-)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8