Re: Offer to clean up (very) old Tracker issues
On Fri, Sep 09, 2011 at 10:41:21PM +0200, Reinhold Kainhofer wrote: What I would like to have is some kind of area tag. While going through some bug reports, I notice that many old reports are dealing slurs or with ties. It would make sense to add something like Area-Ties Area-Slurs I believe that Foo-bar conflicts with Foo-baz. I think that regular tags would be enough, if we wanted to do this. This would allow us to show only those bugs that belong to a given area, like all bugs related to lilypond-book. Currently, we have some tags (markup, midi, grace, website), but there is no real system to those tags. That is true. I'm not certain if it's worth trying to make (and implement) a real system to these tags, though; that's a lot more effort than we're currently thinking of doing on the issues. And I still have some hope that James will return to documentation work at some point, just so that we can have at least one person doing docs! But if you (or anybody) want to make an official list of tags, I'm certainly willing to discuss it. I don't think these tags should duplicate the existing Type- labels, though, so area-documentation should not appear in the list. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
2011/9/8 Peekay Ex pkx1...@gmail.com: Hello, I've had a brief conversation with Graham who agreed in principle and asked me to send a mail to dev regarding 'going through' and 'cleaning up' old tracker issues. that's very nice of you! So I am running this pass the 'dev' group for any other additional suggestions (such as other labels I could remove/apply, how far forward I should go etc) I think Graham said everything that could come to my mind. cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
Am Friday, 9. September 2011, 22:06:07 schrieb Janek Warchoł: So I am running this pass the 'dev' group for any other additional suggestions (such as other labels I could remove/apply, how far forward I should go etc) I think Graham said everything that could come to my mind. What I would like to have is some kind of area tag. While going through some bug reports, I notice that many old reports are dealing slurs or with ties. It would make sense to add something like Area-Ties Area-Slurs Area-LilypondBook Area-MusicXML Area-Gregorian Area-Tuplets Area-Documentation Area-Lyrics Area-PageLayout Area-Libraries (for external libs like pango, guile, etc.) Area-Dynamics Area-Webpage Area-Installer Area-GUIs (or Area-Editors) Area-PartCombine Area-Font Area-SVG ... This would allow us to show only those bugs that belong to a given area, like all bugs related to lilypond-book. Currently, we have some tags (markup, midi, grace, website), but there is no real system to those tags. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
2011/9/9 Reinhold Kainhofer reinh...@kainhofer.com: Am Friday, 9. September 2011, 22:06:07 schrieb Janek Warchoł: So I am running this pass the 'dev' group for any other additional suggestions (such as other labels I could remove/apply, how far forward I should go etc) I think Graham said everything that could come to my mind. What I would like to have is some kind of area tag. While going through some bug reports, I notice that many old reports are dealing slurs or with ties. It would make sense to add something like Area-Ties Area-Slurs Area-LilypondBook Area-MusicXML Area-Gregorian Area-Tuplets Area-Documentation Area-Lyrics Area-PageLayout Area-Libraries (for external libs like pango, guile, etc.) Area-Dynamics Area-Webpage Area-Installer Area-GUIs (or Area-Editors) Area-PartCombine Area-Font Area-SVG ... This would allow us to show only those bugs that belong to a given area, like all bugs related to lilypond-book. Currently, we have some tags (markup, midi, grace, website), but there is no real system to those tags. Maybe... At least it would be good to make sure that the summary of the issue contains the key words (and that the key words are used consistently, for example choose tie or ties, do not use both). cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Offer to clean up (very) old Tracker issues
Hello, I've had a brief conversation with Graham who agreed in principle and asked me to send a mail to dev regarding 'going through' and 'cleaning up' old tracker issues. At the moment we have 580-something tracker issues of which some haven't been 'touched' for a very long time, there are also items with 'owners' who no longer actively (as far as I can tell) work on LilyPond anymore. My intention at first is to 1) Remove erroneous 'Owner' and 'Status' labels (and CC if appropriate). and 2) For those 'issues' that I understand see if the issue still applies to the current (un)stable release (e.g. Glyph X collides with Glyph Y when I x in version 2.really.old) However this will probably generate a fair few auto-emails and I don't want to step on anyone else's toes such as other tracker-sniffers (Messrs Campbell and O. Redchuk). So I am running this pass the 'dev' group for any other additional suggestions (such as other labels I could remove/apply, how far forward I should go etc) or disagreements and this would be a bad idea. Thanks. -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
However this will probably generate a fair few auto-emails and I don't want to step on anyone else's toes such as other tracker-sniffers (Messrs Campbell and O. Redchuk). So I am running this pass the 'dev' group for any other additional suggestions (such as other labels I could remove/apply, how far forward I should go etc) or disagreements and this would be a bad idea. There's already a large amount of `confirmed' tracker messages sent to the list, so I think we can suffer a few more :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
Hi James (or is it Peekay now! ;) I've had a brief conversation with Graham who agreed in principle and asked me to send a mail to dev regarding 'going through' and 'cleaning up' old tracker issues. Good idea! However this will probably generate a fair few auto-emails and I don't want to step on anyone else's toes such as other tracker-sniffers (Messrs Campbell and O. Redchuk). So I am running this pass the 'dev' group for any other additional suggestions (such as other labels I could remove/apply, how far forward I should go etc) or disagreements and this would be a bad idea. A couple of comments: Try to do all changes to an issue at once so we get only one email per issue. Limit yourself to, say, 20 a day, or it will be bad for our healths. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
On Thu, Sep 08, 2011 at 08:25:25AM +0100, Peekay Ex wrote: 1) Remove erroneous 'Owner' and 'Status' labels (and CC if appropriate). The status should almost always be Accepted. If the Owner is me or Valentin, that should be removed (it was an artifact of an old system) unless the issue has a patch by either of us or it is marked as Status-started. 2) For those 'issues' that I understand see if the issue still applies to the current (un)stable release (e.g. Glyph X collides with Glyph Y when I x in version 2.really.old) Yes. Please add bug still in 2.15.10 in those cases. If the graphical output has changed, also add a png. Dmytro has a very nice script that produces better pngs -- some of the old reports have a pdf; please replace that with a png. 3) carefully consider the 'Type' label. (the CG page on issue clarification needs revision, but the GOP-PROP on issues priorities is correct. I hope to fix the CG later today) Most notably, somewhere between 20% - 60% of type-defect issues should be type-ugly now. 4) remove the Priority label 5) to avoid fatigue, both on your part and the part of people reading bug-lilypond, I'd suggest no more than 10 issues each day. Yes, it'll take two months to go through the entire list, but there's no particular urgency for this. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
On Thu 08 Sep 2011, 09:53 Graham Percival wrote: Yes. Please add bug still in 2.15.10 in those cases. If the graphical output has changed, also add a png. Dmytro has a very nice script that produces better pngs -- some of the old reports have a pdf; please replace that with a png. Dmytro?-) Here is it: https://raw.github.com/gperciva/lilypond-extra/master/bug-squad/trimtagline.sh https://raw.github.com/gperciva/lilypond-extra/master/bug-squad/trimtagline.bat -- Dmytro O. RedchukEasy to use is easy to say. Bug Squad -- Jeff Garbers ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Offer to clean up (very) old Tracker issues
On 11-09-08 01:25 AM, Peekay Ex wrote: Hello, I've had a brief conversation with Graham who agreed in principle and asked me to send a mail to dev regarding 'going through' and 'cleaning up' old tracker issues. At the moment we have 580-something tracker issues of which some haven't been 'touched' for a very long time, there are also items with 'owners' who no longer actively (as far as I can tell) work on LilyPond anymore. My intention at first is to 1) Remove erroneous 'Owner' and 'Status' labels (and CC if appropriate). and 2) For those 'issues' that I understand see if the issue still applies to the current (un)stable release (e.g. Glyph X collides with Glyph Y when I x in version 2.really.old) However this will probably generate a fair few auto-emails and I don't want to step on anyone else's toes such as other tracker-sniffers (Messrs Campbell and O. Redchuk). So I am running this pass the 'dev' group for any other additional suggestions (such as other labels I could remove/apply, how far forward I should go etc) or disagreements and this would be a bad idea. Thanks. Good man yourself, Peekay! That backlog had been weighing a bit on my mind, too. Perhaps Abandoned should mean Closed. BTW, you look rather familiar; any relation to the Exes in the Lowe Country? Cheers, Colin -- The human race has one really effective weapon, and that is laughter. -- Mark Twain ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
