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 <grobme...@gmail.com> wrote: > 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 <lukaszlen...@apache.org> >> 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:20 GMT+02:00 Paul Benedict <pbened...@apache.org>: >>> >>>> Back in the 1.x days, we signed releases (the jars, zips, etc.). I >>>> >>> don't >>> >>>> know if we always did, but I did when I was release manager. Is that >>>> practice still in force? ... And do we do that for Struts 2 as well? >>>> >>>> Cheers, >>>> Paul >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >>> For additional commands, e-mail: dev-h...@struts.apache.org >>> >> >> -- >> Sent from my mobile phone >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
