On 05/13/2013 05:43 PM, Nick Coghlan wrote:
Beaker has been doing 0.x releases for a long time. We've been
talking
about the release later this month being 1.0, but before we declare
we've reached that milestone, I'd really like us to be at the point
where someone could reasonably expect to grab the Beaker RPMs from
beaker-project.org, and using just our documentation, set up and start
running their own Beaker instance, including writing new tests using
either beah or autotest.
We're not there yet, and we're not going to get there this month, so the
next release will be 0.13 and we'll continue with regular 0.x releases
until we're happy we have something we consider worthy of the "Beaker
1.0" title. I don't think we're all that far away - we may need a 0.14,
but I'll be surprised if we see 0.15.
For planning purposes, I'd like to keep marking the backlog as "1.0" -
the 0.x releases will then just be snapshots that make useful chunks of
functionality available to users, rather than having to wait until we're
done with everything we want to include for the 1.0 milestone.
It turns out I changed the way I was using the milestone field to track
this without actually announcing the change in the meaning of that
field. The dangers of making decisions on IRC when not everyone is there :)
So, the way the target milestone field now works:
A target milestone of "---" means "maybe, someday, we're still
thinking
about it". (time to availability is conceivably in years, unless we just
haven't triaged it yet)
A target milestone of "1.0" means "this will be implemented before we
declare any release to be the 1.0 release" (time to availability should
be measured in months)
A target milestone of some particular "0.x" means the bug has been
assigned to be included in that particular release (time to availability
should be measured in weeks)
Occasionally bugs in the last category will be bumped to the next
release, although we'll try to avoid that by only moving them from 1.0
to 0.x once we're confident they can be implemented in that time frame.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Test Automation Team Lead
Beaker Development Lead (
http://beaker-project.org/)
PulpDist Development Lead (
http://pulpdist.readthedocs.org)