Re: F21 schedule: what would you do with more time?

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

 



On 08/22/2013 03:03 PM, Matthew Miller wrote:
Based on discussion at Flock, on the devel mailing list, and in the FESCo
meeting, we are looking for feedback on the idea of a longer release cycle
for Fedora 21 -- not (right now at least) the bigger question of the 6-month
cycle overall, but just, right now, slowing down for a release to get some
things in order.

Specifically, both Release Engineering and QA have clear needs (and even
plans for) greater automatiion, but are also incredibly busy simply doing
the things they need to do _now_ to get the release out the door.

So, FESCo would like to see some specifics, like "If we had one week with
nothing else to worry about, we could have automated generation and upload
of cloud images" (to pick an example I personally care about). Or "with six
months of overall delay, we could have continuous integration testing of a
key subset of rawhide". Or "we could spend a couple of weeks and automate
the new package and review workflow".

What Infrastructure projects would be helped by this? Web and design team,
would slowing down the release focus allow time to work on, oh, say, getting
the Wiki beautiful (or does it not matter)? What else?

As we look at Fedora.next ideas and possibly decide to start implementation
in the F21 timeframe, we will likely find _new_ things that take specific
work. Let's not worry about that right now. What things we do _now_ could be
improved with the investment of some effort?



In the core/baseOS...

Continue systemd integration stuff and other packaging cleanup surrounding the core/baseOS

In the QA community...

Work on implementing and intergrading the QA community member role which replaces proven testers and the bugzappers as well as work with releng and spins to sort out and implementing some form of the spin idea I had as well and work with Anaconda team to come up with some kind of testing plan and timing since it's quite time consume trying to be testing the installer at the same time we are working with package and other testing.

In a perfect QA world the installer release would be done at branch and or no later then alpha.

In the server community

Working with and implementing some of my ideas to further build and mobilise the server community.

JBG
--
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