You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Maurice Amsellem <ma...@systar.com> on 2014/03/14 14:01:30 UTC
Release Process
Hi,
I have < lived > two releases of Apache Flex as a team member (4.11 and 4.12) and noticed that whatever the level of testing we make before delivering, we always have issues and regressions after the delivery
So could we envisage to have "beta" releases , like most software vendors, or is it against Apache way ?
Thoughts?
Maurice
RE: Release Process
Posted by Maurice Amsellem <ma...@systar.com>.
Ok thnaks
-----Message d'origine-----
De : Justin Mclean [mailto:justin@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 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 ide directory.
> Also , the WIKI mentions a number of sh (tag_release_candidate.sh
> X.Y.Z, etc.) Where are they located ?
The build directory.
Thanks,
Justin
Re: Release Process
Posted by Justin Mclean <ju...@classsoftware.com>.
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 ide directory.
> Also , the WIKI mentions a number of sh (tag_release_candidate.sh X.Y.Z, etc.)
> Where are they located ?
The build directory.
Thanks,
Justin
RE: Release Process
Posted by Maurice Amsellem <ma...@systar.com>.
>If you wait a few weeks you may want to decide which changes you pull into the the 4.12 branch.
You mean 4.12.1 would be in the "release4.12.0" git branch ?
Or create a new release4.12.1 git branch ?
[ I need to read again the doc on git branching]
>also take a look in the IDE directory I've added a few scripts to make a RM life easier:
They are not referenced in the WIKI. Which script are useful?
> I can help out.
Thanks , I appreciate that.
Also , the WIKI mentions a number of sh (tag_release_candidate.sh X.Y.Z, etc.)
Where are they located ?
Maurice
-----Message d'origine-----
De : Justin Mclean [mailto:justin@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 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 by the release manager (thanks Justin) who can do that efficiently, and without errors.
I can help out. IMO it would be good to have more than one person who's made a release recently,
> 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
It's up to date (part of the release process is to make sure it's up to date) also take a look in the IDE directory I've added a few scripts to make a RM life easier.
Thanks,
Justin
Re: Release Process
Posted by Justin Mclean <ju...@classsoftware.com>.
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 by the release manager (thanks Justin) who can do that efficiently, and without errors.
I can help out. IMO it would be good to have more than one person who's made a release recently,
> 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
It's up to date (part of the release process is to make sure it's up to date) also take a look in the IDE directory I've added a few scripts to make a RM life easier.
Thanks,
Justin
RE: Release Process
Posted by Maurice Amsellem <ma...@systar.com>.
>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:nicholas@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.amsellem@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:justin@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
>
Re: Release Process
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
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.amsellem@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:justin@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
>
Re: Release Process
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Fri, Mar 14, 2014 at 2:47 PM, Maurice Amsellem <
maurice.amsellem@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 ?
>
>
Any committer can cut a build and propose a release at any time. If the
vote passes (3 +1 votes more than -1 votes), we are good to release.
If you have any patches you want to urgently push out, please feel free to
start the process.
Thanks,
Om
> Maurice
>
> -----Message d'origine-----
> De : Justin Mclean [mailto:justin@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
>
RE: Release Process
Posted by Maurice Amsellem <ma...@systar.com>.
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:justin@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
Re: Release Process
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Posted by Alex Harui <ah...@adobe.com>.
On 3/14/14 6:01 AM, "Maurice Amsellem" <ma...@systar.com> 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
sure, when we call it a release candidate, not enough folks try it.
BTW, after many Adobe releases, where we did have betas and qa teams, we
still broke stuff.
-Alex