I hate to be that guy, but lets get all the changes so far (even the ones that affect only the release process) and make the one and only release perfect.
All it would take is create a new RC build and upload the artifacts to the dist site. And I propose that votes be carried over from the first RC. Thanks, Om On Fri, Nov 14, 2014 at 5:09 PM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > Well you were right ... it pushed my tag ... was sort of expecting that to > happen automatically ... well ... you never stop learning :-) > > I doubt that it makes sense to release something just for releasing the > changes to the release procedure, so if it's up to me, I don't need another > release ;-) > > I was more thinking of using the lessons learned when releasing other > parts. > > Chris > > ________________________________________ > Von: Alex Harui <aha...@adobe.com> > Gesendet: Freitag, 14. November 2014 22:35 > An: dev@flex.apache.org > Betreff: Re: AW: [FlexJS] First successful build of a FlexJS application > using Flexmojos > > On 11/14/14, 1:13 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > > >Hi, > > > >Actually I did create that tag ... wonder why it wasn't transferred to > >the Apache Git ... do Tags not get pushed automatically? > > I think in Git you need to "push --tags”. > > > > >I would suggest to release the staged ones and use the optimized pom for > >the next release. > > OK, but is there going to be a next release? I was hoping for > one-and-done. > > -Alex >
