Managing Fedora Testing

[Jef Spaleta]

Keith Lofstrom wrote:
> Schedule would be:

How do you make this schedule work without greatly increasing the
length of time needed for the testing phase? 

How does this schedule really take into account the fact the the point
is to track upstream development as much as possible? If fc2
followed this schedule..would we have a 2.6 kernel with selinux or gnome
2.6 in the final fc2 release? A lot of the pieces are moving targets,
does your schedule and the break down really account for that? 

Does your schedule really make room for something as disruptive as
the introduction of selinux? How the hell do you split selinux's affect
into a 'domain'? shoehorning selinux support in is sort of a top to
bottom, front to back, side to side, in to out problem.

-jef