I remember making a pom property to specify the signing key used for a
release, so that won't be hard. Hopefully the git problem will be resolved
by then, but I'll keep that in mind if it's not.
On 23 November 2015 at 16:01, Ralph Goers
wrote:
> Also, the process is going to have to change sligh
Also, the process is going to have to change slightly. Due to restrictions on
git right now we will have to specify a tag of 2.5-rc1 instead of 2.5. This is
because tags can’t be deleted. I believe you can do that by specifying
-Dtag=release-2.5-rc1.
Ralph
> On Nov 23, 2015, at 2:58 PM, Ralph
I’m fine with that Matt. Just make sure the web site is updated with your key.
Actually, it should probably be updated to reflect the key that was used to
sign each release, not just the current one. I wish the ASF had a code signing
key or we had one for the Logging PMC, but we don’t.
Ralph
Sounds like Matt is back in full force! :-)
Gary
On Mon, Nov 23, 2015 at 12:13 PM, Matt Sicker wrote:
> I'd be willing to be the RM again if you'd like.
>
> On 23 November 2015 at 11:28, Ralph Goers
> wrote:
>
>> I think we are getting near time to release 2.5. There are a couple of
>> issues
I'd be willing to be the RM again if you'd like.
On 23 November 2015 at 11:28, Ralph Goers
wrote:
> I think we are getting near time to release 2.5. There are a couple of
> issues I still want to look into. In addition, I’d appreciate any extra
> testing as there are a few new features and chan
I think we are getting near time to release 2.5. There are a couple of issues
I still want to look into. In addition, I’d appreciate any extra testing as
there are a few new features and changes in this release - namely, the items I
added include modifying the configuration change detection mec
