On 2/12/15 3:54 AM, Igor Bondarenko wrote: > I can do it if you don't mind. I've reviewed release script and it's pretty > straightforward, except for two parts:
Cool, go for it :D > > - Don't sure how exactly I can upload the files and signatures to > https://dist.apache.org/repos/dist/dev/allura/, do I have access? That is an SVN repo, and as an Allura PMC member you should have access. > - Seems like my PGP key must be added to > http://www.apache.org/dist/allura/KEYS in order to make a release That also comes from an SVN repo. https://dist.apache.org/repos/dist/release/allura/ is the source. (That repo automatically gets published out to the www.apache.org/dist periodically) > > Do we have a guide for those two? > > On Wed, Feb 11, 2015 at 7:23 PM, Dave Brondsema <[email protected]> wrote: > >> Heith (relatively new contributor) discovered an issue with logout links >> and as >> provided a fix. https://forge-allura.apache.org/p/allura/tickets/7831/ >> I have >> merged that to master just now. >> >> This seems like a significant enough issue to warrant making our next >> release >> now. I'm happy to do so, but would also welcome anyone else to do it. The >> script at scripts/asf-release.sh makes it very easy. The hardest part is >> summarizing and organizing tickets into a nice changelog :) >> >> -- >> Dave Brondsema : [email protected] >> http://www.brondsema.net : personal >> http://www.splike.com : programming >> <>< >> > -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
