On 8/18/2011 10:29 AM, Eric Covener wrote:
> CHANGES says that currently nothing is backported to 2.2.x since
> 2.2.19 -- should we burn a release # to replace? Can the existing
> release be re-signed in-place?
Hmmm... although I'm happy to re-sign, this is a flaw in gpg; the sig
was valid at the
IMHO it can be resigned in place since we do not touch the release artifacts
itself.
But as Bill did the release IMHO he should resign the release to be consistent
with the
other metadata of this release (e.g. the creator of the 2.2.19) tag.
Regards
Rüdiger
> -Original Message-
> From
CHANGES says that currently nothing is backported to 2.2.x since
2.2.19 -- should we burn a release # to replace? Can the existing
release be re-signed in-place?
-- Forwarded message --
From:
Date: Thu, Aug 18, 2011 at 9:29 AM
Subject: DO NOT REPLY [Bug 51679] New: Code signatu
