From: Silvan <dmm...@us...> - 2005-10-12 18:28:40
|
It's been a long time since we released, and Chris and I are starting to get fired up over notation issues. We're in danger of getting side-tracked, I think. Maybe the thing to do is release 1.1 after all, and do it as something like a somewhat feature-stripped subset of the STG branch. That way STG can keep a little "ahead of the official release" edge to it, but we can let some of the most important bug fixes (also in HEAD) get into the hands of the common users who run distro packages; which is probably at least half of our user base. It's bordering on reproachful how we have failed to put forth maintenance point releases that incorporate serious bug fixes, but it's probably too late to start that now for the 1.0 cycle. So, do a 1.1, use the old canvas, some new bug fixes, and most especially a fix for the auto timer bug that keeps coming up again and again on the user list. A *lot* of people are running into that, and I think we really ought to release a fix for it. I think 1.1 could probably be stable a good while with no need for a follow-on 1.1.1, because most of its bugs have been shaken out. Then aim to release 1.2 early next year (realistically) after we've well and truly gotten the new canvas thing shaken out. Every time we think it's ready to go, we find some new problem. Maybe even hold it back until the auto-expanding canvas is working, and everything is functioning correctly; which G could probably get done before next February, I'm guessing. While this is going on on the one hand, let's tear up tiles and rip off the wallpaper in the experimental notation branch, and really work on delivering the next generation score editor. Then we aim to release the newly revamped notation bits, perhaps with Stephen's guitar chord infrastructure folded in by then, as the 2.0 release point at the end of 2006 or the beginning of 2007 (or 2008 or 2020 or 2973... whenever it's ready. :) That's what I'm thinking anyway. Thoughts? My main theme here is to buy us some time to work, because we're not going to get anything done fast, and we're really holding back important improvements from the users forcing them to wait until we have time to really get a proper 1.2 put together and tested. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Chris C. <ca...@al...> - 2005-10-12 20:43:46
|
On Wednesday 12 Oct 2005 19:28, Silvan wrote: > So, do a 1.1, use the old canvas, some new bug fixes, and most > especially a fix for the auto timer bug that keeps coming up again > and again on the user list. I actually think we should be able to release a 1.2 with the new canvas in a couple of weeks. Guillaume's fixed pretty much all the serious bugs I filed -- that just means it's time to look for some more, of course, but I'm feeling pretty good about it now. We iron out all the bugs we can hit before then, and we remain prepared to do a 1.2.1 soon afterwards if we find we missed something important. So we call this one 1.2 and release it with exactly the same feature set as is currently found in STG (which is also nominally at RG 1.2). The implementation for the segment canvas behind the scenes is different, but all the features are identical. > While this is going on on the one hand, let's tear up tiles and rip > off the wallpaper in the experimental notation branch, and really > work on delivering the next generation score editor. Then we aim to > release the newly revamped notation bits, perhaps with Stephen's > guitar chord infrastructure folded in by then, as the 2.0 release > point at the end of 2006 or the beginning of 2007 (or 2008 or 2020 or > 2973... whenever it's ready. :) > > That's what I'm thinking anyway. Thoughts? I agree pretty much with the rest. The main other (unrelated) thing that would be nice to have in the next major release is automation for mixers and other controls. Chris |
From: Silvan <dmm...@us...> - 2005-10-12 21:07:58
|
On Wednesday 12 October 2005 04:45 pm, you wrote: > I actually think we should be able to release a 1.2 with the new canvas > in a couple of weeks. Guillaume's fixed pretty much all the serious Yeah, but we've been saying that for three months. :) > I agree pretty much with the rest. The main other (unrelated) thing > that would be nice to have in the next major release is automation for > mixers and other controls. Better audio file management too. I was going to launch off on a mission to solve all those problems, spurred on by having just finished my book, and it came to naught. We really need to hash that stuff out too. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Guillaume L. <gla...@te...> - 2005-10-12 21:32:17
|
On Wednesday 12 October 2005 23:07, Silvan wrote: > On Wednesday 12 October 2005 04:45 pm, you wrote: > > I actually think we should be able to release a 1.2 with the new canvas > > in a couple of weeks. Guillaume's fixed pretty much all the serious > > Yeah, but we've been saying that for three months. :) Come on, the last bugs I've had to fix were related to the audio previews, except for one which was a resize problem. None were serious enough as to cause crashes or loss of work. Did you had any crash recently ? As for lifting the composition size barrier, I'd rather do that after the release. It shouldn't be too difficult, but I'm not sure of all the implications throughout the code. -- Guillaume. http://www.telegraph-road.org |
From: Alexandre P. <ale...@gm...> - 2005-10-13 13:03:08
|
On 10/13/05, Chris Cannam <ca...@al...> wrote: > So we call this one 1.2 and release it with exactly the same feature set > as is currently found in STG (which is also nominally at RG 1.2). Okay, let's pretend I'm a new user or developer who wants to grab the most recent code to help with testing/development. Say, I have suspision that there are several CVS branches ot there. 1. How should I find out what branches there are to 'cvs co -r' them? 2. How should I find out, which one is for what purpose? STG acronym doesn't tell me anything. Could somebody please update http://www.rosegardenmusic.com/getting/ with appropriate information? Example: There are several branches in CVS where development is taking place. 1. Branch "A". Its purpose is... . In order to grab it do.... 2. Branch "B". Its purpose is... . In order to grab it do.... This will save someone's time. I judge by my own bitter experience. Alexandre |
From: <aa...@ek...> - 2005-10-13 16:05:14
|
Alexandre Prokoudine wrote: > On 10/13/05, Chris Cannam <ca...@al...> wrote: >>So we call this one 1.2 and release it with exactly the same feature set >>as is currently found in STG (which is also nominally at RG 1.2). > > Okay, let's pretend I'm a new user or developer who wants to grab the > most recent code to help with testing/development. Say, I have > suspision that there are several CVS branches ot there. > > 1. How should I find out what branches there are to 'cvs co -r' them? > 2. How should I find out, which one is for what purpose? STG acronym > doesn't tell me anything. This voices exactly what was going through my mind after reading the above quoted post. (Though I have STG figured out now.) Aaron Spike |
From: Stephen T. <st...@to...> - 2005-10-13 03:10:00
|
The chord tab editor will be a 1.2 item in my opinion. The term is half way done and I will be looking at fixing the editor add/delete notes or barres this Sunday. I need to think how the behavior of a add and delete should work for each of these. Stephen |