On 06/05/2013 01:19 PM, Raymond Mancy wrote:
----- Original Message -----
> From: "Nick Coghlan" <ncoghlan(a)redhat.com>
> To: beaker-devel(a)lists.fedorahosted.org
> Sent: Wednesday, June 5, 2013 1:10:09 PM
> Subject: Re: [Beaker-devel] The march towards Beaker 1.0
> 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)
>
Ok Just to be clear, are we talking about the 'Target Milestone' drop down,
or the 'Flags', or both ?
The RH internal flags are just used for the "---" -> "1.0"
transition.
Once something has been flagged for 1.0 moving it around between 0.x
releases is up to us without messing with the flags any further. While
the final call on which release we target for a fix or feature does rest
with me, I'm definitely open to suggestions about things that should be
included and things which should be delayed (usually because they end up
being harder than we expected), either here or through the internal
planning meetings.
Integrating a couple of different internal processes with each other
*and* a public open source project is certainly an interesting exercise,
so I expect it's going to be quite a while before we get to something
that's relatively stable :)
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)