Andrew John Hughes
gnu_andrew at member.fsf.org
Tue Feb 24 17:14:04 PST 2009
2009/2/25 Joe Darcy <Joe.Darcy at sun.com>:
> On 02/24/09 03:41 PM, Matthias Klose wrote:
> Mark Wielaard schrieb:
> One of the things we discussed at Fosdem was how to coordinate releases.
> We agreed that in principle everybody should be able to "call a
> release", at least for IcedTea6. In principle that tree should always be
> in releasable state. That said, it is still a good idea to have a
> stabilization period, where no new features are added, and only
> (regression) fixes are done. But this also shouldn't block all other
> If I did understand Joe correctly at Fosdem, there are no new code drops
> for OpenJDK6, however he mentioned creating the tags instead. How should we
> forward with this scenario? Should a tarball be hosted on the icedtea
> website as
> We will continue to have changes in the upstream OpenJDK 6 repository;
> periodically these will be tagged with a build number as done in JDK 7.
> (Several of the recent changes should remove the need for a few of the
> IcedTea patches.)
> The current in-progress build is b16. The b15 tag isn't present at the
> moment, but b15 was just used to mark the transition to Mercurial without
> any other code changes.
> If there is interest in having source snapshots in addition to the Mercurial
> forest, we can could consider continuing to provide that in the future.
I believe source snapshots would make things easier, and they are
provided for 7.
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
More information about the distro-pkg-dev