On 04/11/10 17:11, Matthias Klose wrote: > On 04.11.2010 16:29, Robbie Williamson wrote: >> What if we had a ToolchainFreeze, that covered GCC, Java Libraries, and >> Python... > > We already have this, by doing the toolchain upgrades at the beginning > of a release cycle. A formal freeze would mean to disallow bug fixes > too. > >> as changing any one of the 3 late in cycle can lead to extreme >> pain and suffering? > > I'm not aware of any "extreme pain and suffering" during the last > release cycles, besides where we did have planned updates. > <SNIP>
We released axis2c in Maverick which FTBFS, which seems to have been caused by a sensible fix to the toolchain. I was under the impression previously a FTBFS for a main package was considered release blocking. Fixing an issue in the toolchain is a good thing, but it does seem we need better CI to identify issues such as this. Whilst this isn't quite 'extreme pain and suffering', I was attempting to fix this at silly o'clock at night; which I would have liked to have avoided. Kind Regards, Dave Walker -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
