> How do you merge back into develop easily? That's here there is something I don't know, what should be merged back to the develop branch ? We haven't got hotfixes and if something goes wrong with the RC, it is fixed on the dev branch and another RC is done, right ? Even if we would fix on the RC, only this fix should be merged back or I'm wrong ?
What else ? -Fred -----Message d'origine----- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 5 septembre 2013 04:05 À : dev@flex.apache.org Objet : Re: Nighly builds and releases HI, > What was the problem exactly ? One of the RCs had a build number of 0. The file in question was in gitignore so the difference wasn't picked up until a RC had been made and several people had tested it. > why attributing a build number only at release time would make it harder How do you merge back into develop easily? Isn't it simpler not to have exceptions, rather than say merge all files except these ones. The release process is complex enough as it is and we're had zero people other than me to step forward to do a release (past the initial 4.8 one) because of that. Thanks, Justin
