>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: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 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
