[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: The Drive to 1.5

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-07-13 15:56:22 CEST

Daniel Rall wrote:
>> A lot of issues already have the "1.5" milestone (meaning "must be
>> resolved before 1.5 is released") and some have the "1.5-consider"
>> milestone (meaning "nice to have resolved before 1.5 is released").
>>
>> Ideally, all the issues with "---" as their milestone would get
>> examined and assigned a real milestone, either one of the above two,
>> or "1.6", ..., or "unscheduled", "2.0", or "nonblocking".
>>
>> Basically, "unscheduled" just means "someone has look at this and
>> couldn't think of a milestone it had to go in". The difference
>> between that and "---" is that "---" means no one has attempted to
>> milestone it yet.
> ...
>
> Should this formula go into HACKING, maybe here?:
>
> http://subversion.tigris.org/hacking.html#release-stabilization

+1 on adding our issue tracker milestone meanings and triage process to
HACKING, but I'd say just make a new section thereof (and maybe reference it
from release-stabilization.

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Fri Jul 13 15:55:45 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.