On 08/23/2013 07:24 PM, Ted Felix wrote: > I think the confusion is just due to having two pages that appear to > be for the next release. How about just a single "next version" page. > Maybe it will gain a version number as we draw nearer to a release.
I guess where all this came from is that once upon a time we had enough things going on to fork off a release branch. Once we did that, we knew that release was going to be 14.92, say, and the 14.92 page would get edited for things that took place there, whereas next_version remained to cover anything that wasn't going to be merged over into the present release, like more experimental structural stuff or whatever that might need longer to cook. Dealing with a separate release branch died a long time ago, because the problem I'm talking about on the release notes now used to happen with translations back then. One guy translates this version, another guy translates that version, nobody reads the instructions before jumping in; now I've got to merge all that crap together without losing anything, which is a lot harder than it sounds. This wiki think is SUPER easy by comparison. I'm just mentioning the problem so we can figure out some best practices and turn a minor problem into no problem at all. I'm lazy, and I hate doing things twice. For now, let's just agree to edit the 13.08 page, even if we end up calling the release 13.10. In the future, what do you think about running next_version until an actual release is foreseeable, and then once the xx.xx page exists, replace next_version with a DO NOT EDIT page. That ought to make it clear enough. -- D. Michael McIntyre ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
