On Friday 31 of January 2014 08:43:34 Michele Calgaro wrote:
Well, that was the idea basically. In more detail:
- once we think we are ready, we tag RC1.
- work can continue as usual on the main trunk, but new changes will not
make it to R14.0.0 3) any patch that is related to R14.0.0 (blocker, critical bugs) will have to be backported to the RC1 branch. 4) once we are ready, RC1 will turn into RC2 and eventually RC3 5) once we are happy, we tag R14.0.0, then build and release (which is probably going to take one and half months anyway)
Yes, exactly this way I also intended.
However, there's a technical hitch. Nightly-builds are designed to "always" built from "master" branch. This means that for the "stable" builds I'll need now create a new PPA - as was the 'axis' for v3.5.13-sru branch. For release the final R14.0.0 packages would then be used packages from my PPA, not packages from nightly-builds.
Because armel and armhf now building very fast, building 'stable' packages is not a fundamental problem. Unfortunately I do not know if is now on the build-farm enough space to be able to create a new 'stable' PPA in my account.
Tim, please, what do you think about this?
Slavek --