Jesse Keating wrote, at 10/06/2010 07:27 AM +9:00: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > As you might be aware, there was a period of roughly two weeks where a > gcc build (gcc-4.5.1-3.fc14) in the buildroots for both Fedora 14 and > Fedora 15. Items built with this could have undefined behavior, which > could lead to data corruption. > <snip> > > To handle the F14 scene I've come up with this strategy: > * For things tagged in dist-f14 and no newer build elsewhere, do a bump, > build and tag directly into dist-f14. While there is some risk of > breakage, it is quite minimal and with discussion from QA we are willing > to take that chance. This work is ongoing. > > * For things tagged in dist-f14-updates-testing, do a bump, build and > then edit the bodhi ticket to add the new build, and re-push to > updates-testing. This work will begin soon. > > * for things tagged in dist-f14-updates-candidate, do a bump and build. > Then look for an open bodhi ticket for that package, adjusting as > needed. If no bodhi ticket is found, do not create a new one, just > leave the build as is. This work will begin soon. > How does this strategy go for packages that the latest dist-f14 one was rebuilt using gcc-4.5.1-3.fc14, and there is newer dist-f14-updates-candidate one rebuilt using gcc-4.5.1-3.fc14 but no bodhi submission yet? Regards, Mamoru -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
