I am going to hit a speed bump here. I haven't signed anything in years and
I don't have the time right now to re-learn what needs to be done. If I
stage the S1 artifacts, can another committer download them and sign them?
Then we can call a vote.
Cheers,
Paul
On Tue, Jun 24, 2014 at 8:55 AM, P
Thanks everyone. I am just breaking the rust off of my release manager
skills. I'll see what I can do.
Cheers,
Paul
On Tue, Jun 24, 2014 at 8:52 AM, Christian Grobmeier
wrote:
> Its actually even required by ASF policy to sign releases:
> http://apache.org/dev/release.html#what-must-every-rel
Its actually even required by ASF policy to sign releases:
http://apache.org/dev/release.html#what-must-every-release-contain
On 24 Jun 2014, at 11:31, Rene Gielen wrote:
Correct, unsigned releases won't make it to central.
On 24. Juni 2014 07:06:46 MESZ, Lukasz Lenart
wrote:
I think yes
Correct, unsigned releases won't make it to central.
On 24. Juni 2014 07:06:46 MESZ, Lukasz Lenart wrote:
>I think yes
>https://repository.apache.org/content/groups/public/org/apache/struts/struts2-core/2.3.16/
>
>and this is verified by Nexus during Closing repository (I think)
>
>2014-06-24 3:2
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/17#issuecomment-46940928
Done :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
en
Github user kmichae1 commented on the pull request:
https://github.com/apache/struts/pull/17#issuecomment-46940870
I don't know how exactly to "link" to the issue, but I created:
https://issues.apache.org/jira/browse/WW-4363
---
If your project is set up for it, you can reply to
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/17#issuecomment-46938658
Can you create JIRA ticket and link this PR to it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
