Re: New Status "Shelved" in LilyPond Bug Tracker

2017-12-14 Thread David Kastrup
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 Is

Re[2]: New Status "Shelved" in LilyPond Bug Tracker

2017-12-14 Thread Trevor
James Lowe wrote 13/12/2017 12:14:59 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

Re: New Status "Shelved" in LilyPond Bug Tracker

2017-12-13 Thread James Lowe
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 re

Re: New Status "Shelved" in LilyPond Bug Tracker

2017-12-11 Thread Urs Liska
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

New Status "Shelved" in LilyPond Bug Tracker

2017-12-11 Thread 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. ATM only one