> > I seems to me there will always be some people using old > versions of Rosegarden with this bug -- a closed bug report > would help remind everyone the bug is now fixed.
I doubt it. If someone complains about it we will either remember it's been fixed and tell him to upgrade, or if we've forgotten about it we'll just check if it's still there in current CVS, and then tell him to upgrade. Given the abysmal search capabilities of sforge we're unlikely to use it for this kind of "fuzzy" bug search (like "let's see if we had a bug which looks like this") - I know I never do. The only way bug search on sforge can work is when you know exactly what you're looking for. So checking against current CVS will always be faster than looking up sf tracker. Plus I think at least half of the bugs we fix are never even logged on sforge. We keep the tracker for the really hard ones or as fancy todo lists, not for archival purposes. > Out of > interest, do you normally filter out closed bugs on the sf > tracker when you're using it? Yes, of course. -- Guillaume http://telegraph-road.org ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
