On Tue, 10 Jul 2007, Karl Fogel wrote:
> "David Glasser" <glasser@mit.edu> writes:
> > This is the first release cycle I've been around for the beginning
> > of... do we also want to do some triage/milestone-setting in the issue
> > tracker at some point?
>
> It would probably help.
Yeah, we're going to need to do this.
> 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
- application/pgp-signature attachment: stored
Received on Fri Jul 13 02:01:41 2007