N might change later if we feel it should be larger but even for 3 days we should not freeze trunk.
See here: http://www.codesimplicity.com/post/open-source-community-simplified/ Gabor On Thu, Feb 10, 2011 at 3:09 PM, Zeno Gantner <zeno.gant...@gmail.com> wrote: > Hi, > > if N is that low, we can also just freeze trunk for that time. > Or are there good reasons to not do this? > > Best regards, > Z. > > On Thu, Feb 10, 2011 at 1:52 PM, Gabor Szabo <szab...@gmail.com> wrote: >> As we discussed on IRC we would like to improve the quality of Padre >> and the stability of the releases. So we thought to change the release >> process slightly to allow for us to check the release candidate and fix >> show stoppers. >> This will also provide extra time for the translators to catch up with the >> strings for the releases. >> This will also provide time for the release manage to write the release >> notes. >> >> If agreed then this would be the process >> >> PROPOSAL !!!! (based on http://padre.perlide.org/trac/wiki/Release ) >> ================================================= >> >> >> 1) Release manager >> updates messages,pot, >> tidies up code, >> closes Changes file >> 2) creates a branch for the release >> 3) On trunk >> Version number is increased by 0.02 >> Changes file opened >> >> The branch is frozen for N (currently =3) days except for >> - translator updates to .po files. >> - fixing show stopper bugs in the code >> >> Translations >> ========== >> The translators will have to make sure they commit their changes to the >> branch only and they don't touch the .po files on trunk to make >> the merge easy. >> >> Show stoppers >> ============ >> Everyone is encouraged to use Padre from the release branch to find >> critical issues. If a critical issue is found we open ticket, discuss on the >> channel and/or on the mailing list and decide if and how to fix it. >> >> The fix is then committed to both the branch and the trunk. >> >> Release Notes >> ============ >> They can be written during the freeze period. >> >> >> After the release period ends the Release Manager will release Padre >> from the branch. >> Once it is released the directory of the .po files is merged from the branch >> back to trunk. >> The branch can be then deleted (as there is a copy in tags/). >> >> >> regards >> Gabor >> _______________________________________________ >> Padre-dev mailing list >> Padre-dev@perlide.org _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
