RFC: Spins process changes proposal

Kevin Fenzi kevin at scrye.com
Wed Aug 21 16:18:18 UTC 2013


On Wed, 21 Aug 2013 08:45:59 +0100
Ian Malone <ibmalone at gmail.com> wrote:

> On 20 August 2013 19:29, Kevin Fenzi <kevin at scrye.com> wrote:
> 
> > Each approved spin MUST have at least 1 person fill in a basic spin
> > test matrix for at least 1 TC or RC in order to be shipped with
> > Alpha.
> >
> > If the image fails or there are no test results maintainers can try
> > again at the next milestone, but the image is NOT shipped with
> > Alpha.
> >
> 
> My only question is what happens when something higher up is causing
> all composes to fail, IIRC that was the case for a while for F18. Do
> all the spins have to follow this process to try and maintain approval
> in that case?

Well, if it's causing gnome/kde/dvd/netiso to also fail, the release
would be blocked until thats fixed. Once it is, it should be possible
to test and get out in that release, or the next milestone if that one
is missed. 

In practice when all the images don't compose things get fixed pretty
quickly. 

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20130821/d8406a42/attachment.sig>


More information about the devel mailing list