On Thu, 2005-12-15 at 22:01 -0500, Jeff Spaleta wrote: > That concept has the same infrastructure problems with regard to mixed > buildsystems and self hosting requirement. On top of that mixing > Core+Extras into a single release target while Extras is still a > rolling tree with no established freeze points or releases is going to > be a huge pain in the ass. If rawhide didn't freeze for Core releases > the Core release time would take up russian rulette as a lunchtime > bonding activity. Something very drastic is going to have to be done > with Extras's release model to give any potential community release > engineers for alternative collections a fighting chance at getting > anything out the door. Anyone volunteering to do that kind of release > work with the way things stand is crazy and shouldn't be trusted with > cvs access. Yes, I know there is a lot of work to do to make this happen. Doesn't mean that the work shouldn't be done. I honestly don't think we can continue in the direction we are now, constantly growing Core, constantly fighting what goes in/out, etc.. Things have to get better. Certain restrictions on RHEL have been removed wrt including software that is maintained in Extras, so now there is nothing saying that whats in RHEL MUST be in Core. This changes the way we think about Core quite a bit, and opens the door for more creative ways of dealing with Core vs Extras. Things have to change. The question is do we do it now or later? -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating
