I'd certainly be happy if somebody else volunteered, but I currently _do_ have time to do something. The problem is that we're changing over to a new system of dealing with bugs (one which should provide much more feedback to users). Until the new system is up, I'm just saving all the bug reports; I'll process them later. http://lists.gnu.org/archive/html/lilypond-devel/2006-06/msg00205.html
- Graham On Tue, 20 Jun 2006 21:53:14 +0200 Mats Bengtsson <[EMAIL PROTECTED]> wrote: > This is usually handled by the bug responsible, who sends follow-up > emails both when a bug has been included in the bug tracking database > and when it has been fixed. However, the responsibility has just > shifted so for the moment this doesn't happen. In fact, if you are > interested in taking over that responsibility, I think that everybody > would be happy. > > /Mats > > Quoting Colin Wilding <[EMAIL PROTECTED]>: > > > > > > > I sometimes post details here of bugs that I have found, and on > > other occasions I come across a bug and see that it has already > > been reported. > > > > Is there any straightforward way that I can discover whether a > > reported bug has been fixed in the current version? That would > > help me to plan ahead, and decide whether to look for a workaround > > or just hang on for the next stable version. > > > > Colin > > -- > > View this message in context: > > http://www.nabble.com/Which-bugs-are-fixed--t1817597.html#a4955010 > > Sent from the Gnu - Lilypond - Bugs forum at Nabble.com. > bug > > > > > > _______________________________________________ > > bug-lilypond mailing list > > [email protected] > > http://lists.gnu.org/mailman/listinfo/bug-lilypond > > > > > > > > _______________________________________________ > bug-lilypond mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-lilypond _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
