24 Feb
2014
24 Feb
'14
7:29 a.m.
On Mon February 24 2014 12:55:02 am Michele Calgaro wrote:
Actually, during the weekend I was considering the
question "should we create a branch R14.0.0-alpha" ? The reason for that is to
establish a "base" to work on for moving towards R14 release, with an eye in
preventing new bugs to enter R14.0.0 code.
I support that idea. I will have to create an R14-alpha partition or VM, but that is
doable.
We would have to work on backporting patches from the main trunk when they apply to
directly R14-alpha (almost exclusively bug fixes only), but we've been through this
before with 3.5.13.2. Conversely, any patch directly applicable to R14-alpha gets
concurrently merged into trunk.
Fortunately, there will be no renaming patches backported that we have to reverse before
merging into R14-alpha. All renaming patches stay in main trunk.
Two branches will help us focus on not introducing new bugs into R14.0.0. Frankly, I'm
getting pretty beat up with all the bug reports I keep filing. I don't mind filing the
reports, but we need to get our heads back above the water with respect to R14.0.0.
When ready we simply declare the R14-alpha branch to be the R14-RC1 branch, then RC2,
etc.
--
Darrell