On Tue, Aug 20, 2013 at 06:47:31PM -0500, Dennis Gilmore wrote: > I need to update the documentation. But we need to get to the point > where the releng side is transparent and just happens. The crazy > schedules we have had since f18 have allowed zero time for Release > Engineering and QA to do much in the line of development. this is > entirely a failure of FESCo Without spinning the wheel of blame -- at Flock, we talked about slowing down the crazy train a little bit, probably not for F20 at this point but for F21, specifically so we all have a chance to work on those kind of things. > > resources and or bother to keep spins standing on their own to feets > > so to speak. > I think we can implement what is needed in F20. Releng stopped propping > up spins quite a few releases ago. we have not shipped things that > failed to compose. but things that failed to work have shipped. the > burden on releng really is minimal. So, off-topic for this thread, but let's collect things which we can change which _are_ burdensome for releng or otherwise cause bottlenecks, and put them on the plan for fixing during a theoretical longer release. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
