On Thu, 2013-08-22 at 18:11 -0600, Chris Murphy wrote: > On Aug 22, 2013, at 3:03 PM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: > > > > QA, releng and anaconda are on a more or less permanent iteration > > treadmill from Alpha TC1 onwards, severely limiting the time we have to > > work on anything else. We can only really get substantive work done on > > 'things that are not release validation' in the ~two months (on a > > regular cycle) between FNN Go and FNN+1 Alpha TC1. > > > I'm going to take a wild guess here, QA could probably use a month of > going into a black hole for starters, as in, en vacaciones, no me > contacte. So in reality, that probably translates into maybe a four > day weekend. But how much time do you think QA needs for "things other > than release validation"? So far the push back range is a wee bit > broad, 2 weeks to six months. > > If it needs to be six months, fine. But there's also a risk of losing > a lot of momentum with a six month hiatus. That's why I arbitrarily > came up with 3 months on the high end. There are still positives to > the Fedora pressure cooker (ANOTHER RELEASE NAME IDEA!), a.k.a. crazy > train. The more time we have, the more stuff we can do. We have a list of things we'd like to have that could fill a couple of years of work easy, most likely. I was thinking three months was not arbitrary, but 'the right amount of time to get back into sync with GNOME', which was one of the aims of our six month cycle prior to F18. If we're going to do a 'hiatus', it would seem sensible to use it to get back into a cycle which works nicely with the GNOME dev cycle. (No, I am not going to use the word 'cadence' at any point in this mail. Damni-) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
