+1
Craig R. McClanahan wrote:
Earlier, we had agreed on using the version numbering and release strategy
that httpd and Tomcat are using -- x.y.z milestones would be released
fairly often (your idea of monthly sounds fine to me), without any implied
"quality" metric -- then, they'd get voted on as being alpha, beta,
general release, or broken.
If we go that way, we can certainly start creating the 1.2.1, 1.2.2
milestones -- but I would still suggest we categorize all the existing
LATER entries as either "1.2 Family" or "2.0 Family" first. Such a
designation is NOT an express or implied promise to actually do something
-- only a general grouping.
When a committer volunteers to actually implement one of these tickets in
a particular milestone release, he'd both assign the ticket to himself AND
update the milestone to the specific one (1.2.1, 1.2.2, whiatever) that
its planned to be finished for. So, I will go ahead and create 1.2.x
milestones for the first few ... although I think it's still too early to
talk about any specific 2.0.x milestones at this point.
Does that sound like a reasonable strategy? If so, it should be codified
in our process documentation so that we can point at it.
--
Ted Husted,
Struts in Action <http://husted.com/struts/book.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
