Re: RFC: Spins process changes proposal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 21 Aug 2013 08:45:59 +0100
Ian Malone <ibmalone@xxxxxxxxx> wrote:

> On 20 August 2013 19:29, Kevin Fenzi <kevin@xxxxxxxxx> 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

Attachment: signature.asc
Description: PGP signature

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux