>All we have to do is have somebody package up a release and put it to a vote. >No different than a "regular" release...
I am willing to give it a try for the next point release ( in a few weeks maybe). My concern is that a "regular" release is packaged by the release manager (thanks Justin) who can do that efficiently, and without errors. Justin, from your experience, do you know if the page below is up to date, and just applying step by step would result in a successful release ? https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK Maurice -----Message d'origine----- De : Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Envoyé : vendredi 14 mars 2014 22:52 À : dev@flex.apache.org Objet : Re: Release Process All we have to do is have somebody package up a release and put it to a vote. No different than a "regular" release... -Nick On Fri, Mar 14, 2014 at 5:47 PM, Maurice Amsellem < maurice.amsel...@systar.com> wrote: > That's the point. > Actually I don't care about having betas or not. > My concern is that we know (and it happened) people discover bugs just > after the release, and I think it's too long to wait another 6 months > for the next release. > It's a good idea to make a point release, but it happened only for > 4.9.1, but not for 4.10 or 4.11, although there were some important fixes for > 4.11. > > So how does it happen? committer/PMC proposes to make another release > at some point, and puts it on vote ? > > Maurice > > -----Message d'origine----- > De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi > 14 mars 2014 22:38 À : dev@flex.apache.org Objet : Re: Release Process > > Hi, > > You can have alpha and beta releases under Apache but I don't think it > would help. If we do find a serious bug we can always fix it and make > a point release eg 4.12.1 easily enough. > > Justin >
