maas-devel team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

On Wednesday 07 Nov 2012 15:10:11 Francis J. Lacoste wrote:
> Hi folks,
> 
> There were some confusion around when we should move bugs on the 'maas'
> project to Fix Released.
> 
> I propose the following "simple" definitions:
> 
> Fix Commited: the revisions containing the fix to the bug have been
> merged to trunk. I think everyone gets that one right today.
> 
> Fix Released: the revisions containing the fix are available in the
> 'daily-qa-ok' PPA. The idea is that users consume MAAS through package,
> so we 'Released' should reflect that. And we really don't want users to
> be testing directly against the daily PPA. So the 'daily-qa-ok' which
> means the integration tests pass seems like a good target.
> 
> This only applies for bugs on the 'maas' project. Bugs on the 'maas'
> package should use the regular Ubuntu definition. (Which means IIRC it's
> Fix Released as soon as a package has been uploaded to the appropriate
> archive.)
> 
> Let me know if you have any questions or disagree with the above
> definitions.
> 
> Cheers

Thanks for making this clear Francis (I'd forgotten our discussion in 
Copenhagen!).

In addition to these definitions we should be clear about what bugtasks should 
be on a bug:

 * trunk task
 * If an SRU candidate, a released branch task (e.g. lp:maas/1.2) which should 
have a milestone
 * ubuntu package task

In this case trunk is fix-released as per Francis' definitions, the released 
branch task is fix-released when the milestone is released [1] and the ubuntu 
task is released when the package hits -updates.

[1] The milestone is released when the package hits -proposed, ie. when a 
candidate to test is available.

Still happy with these Francis?

J