On Fri, 2008-08-22 at 14:23 +1200, Amos Jeffries wrote: > We already discussed it way back, you, myself, and Henrik came to the > conclusion that priority milestones rather than time-based ones would be > better for releases.
Can you point to that thread? "Priority milestone" does not ring a bell for me. > > For example, is the following an accurate definition? > > > > Priority value (1 being the highest) may be assigned by the developer > > responsible for the feature to represent the relative value of that > > feature to other Squid projects by that developer. When no developer is > > responsible, the priority may be assigned by the Project to represent > > the overall importance of the feature for developers. Priority has no > > effect on feature acceptance. > > Yes. Maybe a priority 0 'hands off I'm already neck deep into the code > here' as highest though. OK. We can try to use this and see if it helps or hurts. Thank you, Alex.
