Starting a new development and writing code from scratch would be a better proposition than breaking the existing code base.
A proposal:We declare the current trunk to be the "stable" version, and release it as 1.0 (or maybe 1.x since CHDKDE already took 1.0 ?)A branch is created from the stable version, for ongoing bug fixesThe trunk becomes a development branch for 2.xWork continues in the trunk
Is the definintion of 2 & 3 reversed ? Don't you want to do bug fixes (only) in the trunk and new developments in branches ?
Regardless, any thoughts on how the branches get merged back into the trunk ?
Also, is there a "goal" for 2.0, 3.0, 4.0 etc ? Maybe a six month rolling cycle with a code freeze one month before the update ?
My view is that the stable (1.x) branch would still have bug fixes and improvements made (including new ports); but the version number and branch would stay the same.Any bug fixes and improvements would also be done in the main trunk (if applicable).
At some point the trunk is deemed stable, another stable branch is created and the cycle continues. You also need to decide if the 1.x branch then dies and is no longer updated.
We've discussed this in the past, going back and forth without any real conclusion. I don't want to do that again, so unless someone comes up with convincing objections, I'm going to make this this happen in some form before integrating the above mentioned changes in the trunk.
Started by blufade
General Discussion and Assistance
Started by Reverb
Started by RaduP
« 1 2 3 »
Started by Fairbanks
Started by kylefoley76