Hi
On Wed, Jul 30, 2014 at 11:12 PM, Siddhesh Poyarekar wrote:
The problem with that approach is that lots of bugs go unnoticed until
very late in rawhide, resulting in those bugs being caught and fixed
only post-release. ABI. That is, any ABI breakages that happen
are usually bugs. We try to ensure that with a basic ABI checker in
the glibc testsuite and in future we'll be looking to enhance our ABI
checking capabilities. Taskotron (based on a quick read from the
wiki) seems to be a good framework for this.
Yes. My concern is that glibc is using Rawhide as their continuous integration sandbox to shake out bugs as opposed to doing it elsewhere and just taking care of integration of releases when they are ready. If this viewed as a gap that needs to be fixed, that's fine for now.
Rahul
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
