On Wednesday 28 Jun 2006 06:57, Pedro Lopez-Cabanillas wrote: > And that was my proposal, too. If we delay the next release a long time, > because the new featuires require a lot of time for cooking, at least let > the users to have a bugfix release, with no new features but less bugs than > the 1.2.3 release.
My suggestion back when 1.2.3 came out was to do a 1.2.4 stable release shortly afterwards if necessary, and then to do 1.3 in "late spring" with certain selected new features, and do 1.4 or whatever late in the year with notation restructuring and so on. We're still basically looking at those releases, but reconsidering the question of which ones to do and when. For reference this is what I imagine the three releases as containing: 1.2.4: * Bug fixes against 1.2.3 1.3: * Multi-track MIDI recording (but not revised segment instrument scheme) * Ramped tempo and new tempo ruler (with editing (editing not done yet)) * Range cut and paste * Lilypond annotations * Fixes * Anything else? 1.4: * Staff and voice related notation work (me) * Fretboard and tablature (various) * New instrument/segment structure (Pedro) * Matrix canvas rewrite (Guillaume) Three options: [A] Release 1.2.4 ASAP. Continue working in trunk towards 1.4 in a year or so. Skip 1.3 entirely. I think this sounds like what Pedro's suggesting. [B] Tidy up the features that are in trunk already, fix a few more things and put out 1.3 in "a couple of months". Then continue hacking towards 1.4 next year. [C] All of the above, i.e. 1.2.4 ASAP, 1.3 "soon", 1.4 "later". This is basically the original plan plus slippage. I think I probably vote for B. I vote against A because I really want to see some of the features currently in trunk released, and I don't want to wait until the 1.4 timeframe for that. I vote against C because it takes work to get a release out and I'm not sure we have enough fixes in 1.2.4 to justify it if 1.3 can be fairly close, which it probably can. There's also the option of a separate unstable series -- in the above I'm basically thinking of 1.3 as a stable release if possible (i.e. as a potential branch point for a 1.3.1 with bugfixes, rather than as the first in a new 1.3.x unstable series with more new features). I don't really have a view on that at the moment -- if someone wants to suggest dates and contents for such releases, that might make it easier to think about. Chris Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
