> about the technical work which need to be done and which need to change
> the Fedora cycle durations. What, who, when, how long, and why this
> can't be done in parrallel ? All I'm getting is "we need longuer cycles"
> and still not understanding.
>
> BTW I'm not represnting Red Hat position, just an engineer trying to
> understand some engineering plumbing and not getting it.
>
Who: fedora community people along with some red hat release engineers
What: Fedora extras steering committee
Why: We have to re-engineer EVERYTHING that y'all already have in order
to: 1. support systems which are not inside red hat's network
2. have a buildsystem at all
3. have an errata release mechanism at all
4. have a db to coordinate any of these things.
We're not allowed to use or even see anything already written at rh b/c
either: 1. it sucks or 2. it's part of the 'secret sauce' that some vp
at rh thinks is valuable, somehow.
So we have to start over from scratch on everything and only a handful
of those systems are in place:
1. cvs - only took a year to get it happening and another 6 months to
use it
2. account system - only 18 months
3. build system - once extras got moving it took a mere 4 months to
get time to take care of it - and we still have to throw one away.
4. errata system - not there yet - probably AT LEAST another 6 months
5. db for coordination - just starting
oh and we need all of those things YESTERDAY.
So there you go. - that's the list - now do you understand why we would
like a little more time before the next release?
-sv
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-devel-list
