[2.1 RELEASE] Bump to latest changesets and update NEWS

[Andii Hughes]

On 13 June 2012 14:22, Xerxes Rånby <xerxes at zafena.se> wrote:
> 2012-06-08 02:00, Andii Hughes skrev:
>> This bumps the IcedTea 2.1 tree to the latest changesets and updates
>> NEWS to list the ARM changes
>> (items based on the changeset descriptions; improvements welcome).
>> This is in preparation for the
>> upcoming security release:
>> http://www.oracle.com/technetwork/topics/security/alerts-086861.html
>>
>> Ok for 2.1?
>>
>> Changelog:
>>
>> 2012-05-07  Andrew John Hughes  <gnu_andrew at member.fsf.org>
>>
>>       * Makefile.am:
>>         (OPENJDK_VERSION): Bump to b21 (latest in 2.1 tree).
>>          (HOTSPOT_CHANGESET): Sync to HEAD.
>>          (JDK_CHANGESET): Likewise.
>>          (HOTSPOT_SHA256SUM): Likewise.
>>          (JDK_SHA256SUM): Likewise.
>>       * NEWS: List ARM changes.
>>
>>
>
>
> Thank you for the update to bring in the security fixes.
> A last comment before the 2.1.1 release.
> It would be great if we quickly bumped/moved the hotspot change-set to:
> http://icedtea.classpath.org/hg/release/icedtea7-forest-2.1/hotspot/rev/2eed594c7cdb
> in order to include the last ARM http://icedtea.classpath.org/hg/release/icedtea7-forest-2.1/hotspot/rev/07db9a656dea fixes as well.
>
> The security team and arm team do work in parallel as can be seen in this graph:
> http://icedtea.classpath.org/hg/release/icedtea7-forest-2.1/hotspot/graph/2eed594c7cdb
>

The release, as tagged on Thu Jun 07 19:21:20 2012 +0100, has already
had extensive
testing and the tarballs have already been built.  This is a security
update and shouldn't
be delayed further.

I'm aware that you couldn't have known about this back then, but that's
a feature of security updates.  Andrew Haley, who committed that
changeset, was aware
that the release had been tagged (he already asked to do the earlier
move from 6a67d57915ba
to 8b7c4c5f6ba9).

It's preferable that bug fixes don't occur in the same releases as
security updates, so that
users aren't forced to add new fixes/features to get the security
updates.  It also allows the
release process to be much more transparent.  2.2.1 is much closer to
an ideal security
update in this respect (2.2.0 had the features, 2.2.1 has the security
update).  As mentioned
several times, I'd have preferred some of the ARM work to have been
out in a release before now.

The priority with this release is getting the security updates out in
a timely fashion.  You are more
than welcome to follow up with a 2.2.2 release in, say a month's time.
 It would be helpful to have
the PulseAudio fixes on this branch too, for instance.

> Trying to improve the release, cheers.
> Xerxes

Thanks,
-- 
Andii :-)