Well if you guys wouldn't have been so active in accepting donations, we now wouldn't have the work with releasing that stuff ;-) (Just kidding)
Well ... in my pipeline there will definitely be BlazeDS and FlexPMD coming in the near future. But I guess we will use the new flex-ci-build profile in those projects. Chris ________________________________________ Von: Erik de Bruin <e...@ixsoftware.nl> Gesendet: Freitag, 14. November 2014 23:21 An: dev@flex.apache.org Betreff: Re: AW: [FlexJS] First successful build of a FlexJS application using Flexmojos Given the rate at which Chris is contributing, I'm sure we'll have a hard time just trying to keep up with the votes ;-) EdB On Fri, Nov 14, 2014 at 4:17 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 11/14/14, 2:07 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > > >> > >> >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. > >> > > > >Let's not drag this out. This is a utility release, and 'good enough to > >work with' should mean 'good enough to release'. If someone want to > >perfect > >all the itty bitty details later on, he/she is free to do another release. > >Between the Maven magic and the release script, voting was a breeze, so I > >wouldn't mind another release at all. > > > >Let's make releasing stuff easier by not dragging out each vote pending > >minor details and require/request endless RCs, please? This has been > >discussed and consensus was reached to try and relax the protocol a bit, > >right? > > Agreed. My preference is to release what we voted on and not do another > release unless we need to actually change code in one of those 4 java > files. I was just wondering if Chris was expecting that there would be > another release or not. > > -Alex > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
