Re: New Status "Shelved" in LilyPond Bug Tracker
Trevor writes:
> An Issue marked Accepted/Enhancement sounds to me very positive,
> suggesting that there might be hope this could be implemented
> relatively quickly: implying it has been assessed ("Accepted") and
> considered to be a practical and desirable enhancement.
>
> Whereas giving an Issue the status of Shelved makes it plain there are
> absolutely no plans to implement this in the foreseeable future: it
> has not yet been assessed and is not yet Accepted; it is just a marker
> meaning it might be considered at some unspecified time in the future.
>
> Does that accord with your understanding, David?
"Shelved" to me more means like it has been assessed and judged to be
outside of the scope that the assessor would consider justifiable in
effort for a stock LilyPond improving programmer.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Status "Shelved" in LilyPond Bug Tracker
Hello Trevor, On Mon, 11 Dec 2017 16:50:01 +, Trevor wrote: > > Devs and Bug Trackers > > I have implemented a new Status field in the Issues Tracker at > SourceForge: Status:Shelved, with the meaning: > > "Probably desirable, but impractical to implement at present due to lack > of resources". > > There is also a new Search: Open (Shelved) to list them. > > ATM only one Issue has this Status, > https://sourceforge.net/p/testlilyissues/issues/5244/ but there are lots > of other existing issues that could be assigned to it, when someone has > a few spare moments to go through the Issues to find them. Without getting into unnecessary semantics with dictionary definitions etc. how does this 'status' differ, so to speak, from an issue that is simply marked as an 'enhancement' and has the 'Status' field either blank or set to 'accepted'. After all, I suspect that 'many' enhancements (if not all) on our tracker list could be classed as "... impractical to implement at present due to lack of resources" You may also recall a long conversation we all had back in 2015. http://lists.gnu.org/archive/html/lilypond-devel/2015-11/msg00146.html Where I was trying to establish a process for the Patch Meister (i.e. me) to comb through all opened/abandoned trackers and reset statuses accordingly but of course, good intentions and all that, I never did get around to it. N.B It would create a lot of noise for people for those subscribed to one or more of dev, bug and auto lists. I did however find a patch that I was working on at the time, but that I never published for review, to update the CG section on the patch process; but as always I let it get to big and then and then and then and then ... so it sits here 'shelved' as it were on my own PC. Perhaps now is a good moment to revisit all this section again? Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New Status "Shelved" in LilyPond Bug Tracker
Am 11. Dezember 2017 17:50:01 MEZ schrieb Trevor : > >Devs and Bug Trackers > >I have implemented a new Status field in the Issues Tracker at >SourceForge: Status:Shelved, with the meaning: > >"Probably desirable, but impractical to implement at present due to >lack >of resources". > >There is also a new Search: Open (Shelved) to list them. > Thank you. I think this is a good idea. I will create such an issue and upload my assessment when I'll be through wirh my beam subdivision investigation. (I was forced to take a break from this recently). Urs >ATM only one Issue has this Status, >https://sourceforge.net/p/testlilyissues/issues/5244/ but there are >lots >of other existing issues that could be assigned to it, when someone has > >a few spare moments to go through the Issues to find them. > >Trevor > > > >--- >This email has been checked for viruses by AVG. >http://www.avg.com > > >___ >lilypond-devel mailing list >lilypond-devel@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
