Fedora.next in 2014 -- Big Picture and Themes

Kevin Fenzi kevin at scrye.com
Fri Jan 24 17:29:32 UTC 2014

On Fri, 24 Jan 2014 09:58:07 -0700
Eric Smith <spacewar at gmail.com> wrote:

> On Jan 23, 2014 2:33 PM, "Kevin Fenzi" <kevin at scrye.com> wrote:

> > This is not practical. Lots of people are thinking about a
> > fedora.next, qa folks are coding away, lots of people who normally
> > would be working on the next release are not. If we tell them to
> > stop all that and go back to normal, we could, but then fedora.next
> > will likely never ever happen.
> [...]
> > The current problem I have with Fedora.next is that it's so
> > abstract.
> How are QA folks "coding away" for Fedora.next, rather than
> traditional Fedora QA processes, if Fedora.next is "so abstract"?

The things they are working on have been known for years, but our 6
month release cycle with no hope of being able to work on tooling
hasn't allowed them to do so. 

So, things like replacing autoqa with taskotron, investigating beaker
and other items are likely to be very helpful in both a fedora.next
and a 'traditional' fedora world. 

I'll stop talking for them, feel free to join them on the qa-devel
list and offer your help. 

-------------- 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/20140124/7e61cc73/attachment.sig>

More information about the devel mailing list