[development] proposal for issues: post 4.7 marker

Larry Garfield larry at garfieldtech.com
Tue Jan 10 01:10:08 UTC 2006

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 at 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 

More information about the development mailing list