RE: Release Process

2014-03-14 Thread Maurice Amsellem
Ok thnaks -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : samedi 15 mars 2014 00:12 À : dev@flex.apache.org Objet : Re: Release Process Hi, > You mean 4.12.1 would be in the "release4.12.0" git branch ? Yes. > Or create a new rel

Re: Release Process

2014-03-14 Thread Justin Mclean
Hi, > You mean 4.12.1 would be in the "release4.12.0" git branch ? Yes. > Or create a new release4.12.1 git branch ? You could but no real need as current 4.12 is frozen as it was released. > They are not referenced in the WIKI. Which script are useful? Sorry it was the build directory not the i

RE: Release Process

2014-03-14 Thread Maurice Amsellem
urice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : vendredi 14 mars 2014 23:19 À : dev@flex.apache.org Objet : Re: Release Process Hi, If you wait a few weeks you may want to decide which changes you pull into the the 4.12 branch. In that cas

Re: Release Process

2014-03-14 Thread Justin Mclean
Hi, If you wait a few weeks you may want to decide which changes you pull into the the 4.12 branch. In that case you'll need to get Erik to switch the mustella tests over to the 4.12 branch unless you want everything from the release branch. > My concern is that a "regular" release is packaged

RE: Release Process

2014-03-14 Thread Maurice Amsellem
DK 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

Re: Release Process

2014-03-14 Thread Nicholas Kwiatkowski
software.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 >

Re: Release Process

2014-03-14 Thread OmPrakash Muppirala
he process. Thanks, Om > 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

RE: Release Process

2014-03-14 Thread Maurice Amsellem
lasssoftware.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

Re: Release Process

2014-03-14 Thread Justin Mclean
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

Re: Release Process

2014-03-14 Thread Alex Harui
On 3/14/14 6:01 AM, "Maurice Amsellem" wrote: >So could we envisage to have "beta" releases , like most software >vendors, or is it against Apache way ? I don't think it is strictly prohibited by Apache Policy, but I don't think it will help. If we call it a beta, folks may not try it. For su