Re: Pungi 4 milestone builds: proposals

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

 



On Mon, 2016-03-14 at 07:29 -0400, Kamil Paral wrote:
> > 
> > releng flipped any necessary switches for
> > 'release' behaviour.
> I think this is the only meaningful argument for having TC/RC
> distinction. Personally I'm fine with it both ways. It's nice to see
> which images are the ones "almost ready", but I'm not sure it's worth
> having more bits for releng to remember and flip.
> 
> > 
> > 
> > > 
> > > TC's
> > > alpha-0.1
> > > alpha-0.2
> > > alpha-0.3
> > > alpha-0.4
> > > beta-0.1
> > > beta-0.2
> > > beta-0.3
> > > RC-0.1
> > > RC-0.2
> > > 
> > > legit RC's
> > > alpha-1.1
> > > alpha-1.2
> > > alpha-1.3
> > > alpha-1.4
> > > beta-1.1
> > > beta-1.2
> > > beta-1.3
> > > RC-1.1
> > > RC-1.2
> If we keep the TC/RC separation, I like the approach above.
> 
> > 
> > 
> > I think this still works a bit better if we add a 'Final' milestone
> > rather than using the 'RC' milestone, but yeah, this isn't bad.
> "Final" would be nice.

So just as an update on this: Dennis and I had a chat about it this
morning, and it's difficult to be totally sure how we want to handle it
ahead of time, so for now we're inclined to keep it as simple as
possible. I'm going to file a request for an Alpha 'candidate' and
suggest it simply be labelled Alpha-1.1 , and we're going to work on
the assumption we will ditch the TC/RC distinction at least so far as
compose creation goes. We'll do Alpha-1.1, Alpha-1.2, Alpha-1.3 and so
on, without worrying about the TC/RC distinction.

At least that's the initial plan - once we've actually done a couple of
composes and seen what exactly comes out of the sausage machine, and
we've tried to set up validation events for them and seen how it works
for real testing, we can see if anything didn't turn out too well and
needs to change.

For now I'm inclined to similarly try and keep the validation stuff as
simple as possible, so I won't try to recreate the 'TC' / 'RC'
distinction at the validation event level, but instead the events will
follow the Pungi compose versioning quite closely, so we'll have
something like Test Results:Fedora 24 Alpha 1.1 Installation . If that
seems terrible to anyone, please yell now. :)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux