On Friday 16 Jun 2006 11:30, Nick Bailey wrote: > What's the best way of getting this into a mainstream release?
Well, good question. There are various things about the pitchtracker code that suggest it's not an ideal fit for the standard build -- not least that it has a very specific purpose that isn't likely to be of much interest to the general Rosegarden user. It also adds a substantial amount of code, a JACK client to the main GUI application (working quite separately from the existing audio/MIDI interfaces), and a build dependency on fftw. On the other hand, it does only add a single menu function that is easily ignored (I think?), apart from the general quarter-tone notation support (and that part I'd have no problem with rolling in to the default build anyway). My marginal inclination is to say we should merge the code in to the main source release, but make it a compile option that's off by default. Views from others? > [...] the current architecture is up for rewrite, but at a > pretty low priority, so it would make sense to release our stuff in > the interrim (although the last thing we want is to delay the rewrite > further). I think you should ignore any other planned restructuring at this point. More of an issue may be that you'd be well advised to sync up to the current HEAD build before releasing, but the rest of HEAD is not quite ready for another release yet, so that's likely to hold you back. We will definitely do another release before merging any notation restructuring, so the timeline could be something like (a) you merge stuff now, (b) we continue working on other features for the relatively soon 1.3 release, (c) when that's done, we release 1.3 and you announce the optional pitch tracker component, (d) we press on with notation stuff which by then will have a requirement not to break the tracker code. ?? Chris _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
