Proposed IcedTea 6 release

[Andrew John Hughes]

2009/8/8 Mark Wielaard <mark at klomp.org>:
> On Sat, 2009-08-08 at 08:56 +0100, Andrew Haley wrote:
>> IMO we spend far too much time discussing these issues.  We need to make
>> this standard procedure: whenever there are fixes for significant bugs we
>> apply them to the current release branch and make a minor release.
>> Whenever there are significant new features we make a major release.
>> A lot of the discussion in this list is, IMO, a result of confusing
>> these unrelated issues.
>>
>> The ARM port is all ready to go in apart from one minor problem.  This can
>> be fixed in the next few days, I hope, and the testing can begin.
>
> Right. I think the confusion comes from where people think we are in the
> release cycle. It would be good if we had more timed releases, say every
> 6 weeks on a Monday (or something similarly random, but consistent).
> Then it is clear that when the release manager says that a release is
> coming, you know when you must have had your code in, testing done and
> that a branch is imminent.
>
> Otherwise we get situations where there seems to be lots of discussions
> because some people believe we are ready and are in testing mode before
> a final release already and others think we are at the start of a
> release cycle and new stuff can still be added and additional testing
> needs to be done afterwards.
>
> Cheers,
>
> Mark
>
>

+1

It would also be good to coordinate with Sun on this in order to time
IcedTea6 releases against upstream OpenJDK6 build drops.  There is a
known cycle for OpenJDK7
(http://openjdk.java.net/projects/jdk7/calendar/) but none, as far as
I know, for OpenJDK6.
-- 
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

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