proposal for issues: post 4.7 marker
Hi, This is an infrastructure mail, but since it mostly affects developers I chose to mail it here. I tried to make an estimation on how many bugs and features with and without patches are still there, holding up the 4.7 release. It seems rather impossible, so I decided to conclude with "a lot". A solution, could be to add a version "post 4.7". So that we can mark issues that are interesting, but not for now, as post 4.7. I know we have "postponed" but that is hardly used. And more: postponed does not indicate untill when it is postponed. It also cannot co-exist with "patch (code needs work)" and so statuses. Is it possible and usefull to add a tag "post 4.7" where we can reassign issues to? Bèr
On Sun, Jan 08, 2006 at 06:22:53PM -0600, Chris Johnson wrote:
B?r Kessels wrote:
Is it possible and usefull to add a tag "post 4.7" where we can reassign issues to?
B?r
That seems like a good idea to me.
There's already 'postponed' status. -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!
Op maandag 9 januari 2006 11:16, schreef Piotr Krukowiecki:
There's already 'postponed' status.
I wrote: " I know we have "postponed" but that is hardly used. And more: postponed does not indicate untill when it is postponed. It also cannot co-exist with "patch (code needs work)" and so statuses. " -- [ Bèr Kessels | Drupal services www.webschuur.com ]
On 1/9/06, Bèr Kessels <ber@webschuur.com> wrote:
Op maandag 9 januari 2006 11:16, schreef Piotr Krukowiecki:
There's already 'postponed' status.
I wrote: " I know we have "postponed" but that is hardly used. And more: postponed does not indicate untill when it is postponed. It also cannot co-exist with "patch (code needs work)" and so statuses. "
Exactly - this is why we need a "target milestone" field so we can say "targetted to 4.7+" and have a status of "patch (code needs work)" so that information about the availability of code doesn't get lost. And I know talk is cheap and code is gold - I'll check for/add issues for these items today and assign myself. Greg
On Monday 09 January 2006 08:43 am, Greg Knaddison wrote:
Exactly - this is why we need a "target milestone" field so we can say "targetted to 4.7+" and have a status of "patch (code needs work)" so that information about the availability of code doesn't get lost.
And I know talk is cheap and code is gold - I'll check for/add issues for these items today and assign myself.
Greg
That would be extremely useful. If a feature patch is targeted at 4.7, great, let's review it. But if the author says that it's targeted for 4.8 or later, then at least for right now I would rather spend time on patches aimed at 4.7, unless they're extremely cool-looking. :-) This would probably mean patches flagged as "post-4.7 target" won't get as much attention until after 4.7 ships. That is a good thing, as attention should be focused on 4.7-related issues until then. -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
participants (5)
-
Bèr Kessels -
Chris Johnson -
Greg Knaddison -
Larry Garfield -
piotr＠mallorn.ii.uj.edu.pl