SourceForge is starting to make noise about wanting to get projects 
moved over, so they can stop maintaining two codebases.

As I recall, this move is going to wipe out our bug and feature request 
trackers.  That's basically a good thing overall, since it's mostly a 
huge list of real but very minor problems we can't or won't fix, going 
back up to 10 years, and the whole thing smells like a fresh, clean start.

I don't want to interrupt any ongoing issues where the trackers are 
currently and actively being used to manage something, or, at a minimum, 
I should at least make sure to preserve and resurrect whatever issues 
those are in the new setup.

I have a couple of sad side projects.  I'll go experiment with 
converting one of those over before I give additional thought to 
Rosegarden making the switch.  In the meantime, think about what, if 
anything, we need to take with us from the old trackers.
-- 
D. Michael McIntyre

------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to