The first thing I want to do is congratulate Karanbir and Tasha on the birth of their new baby girl Millie. She is the quite cute ... hello Millie :)
The CentOS Project has spent much time and effort into getting a new build system in place for CentOS 6 that can generate good and timely builds, as well as inform us of newly released upstream SRPMS and keep the CentOS QA team informed when we build any new packages.
The release of CentOS-6.2 on 12/20/2011, in less than 2 weeks and at the same time as Oracle's OEL as noted on Distrowatch, is where we would like to have all our future releases be. I think that we should see the standard 2-4 week time frame for point releases and within 24 hours for updates now that we have this new build system in place.
We have also put a Continuous Release (CR) repository in place for both CentOS 5 and CentOS 6. This repository can be installed via the simple command:
yum install centos-release-cr
The purpose of the CR repository is to allow the CentOS Project to push some of the security updates if we are having issues with a point release build (like we did with both CentOS-6.0 and CentOS-6.1). If we are not going to meet the 2-4 week goal for our point release, we will push out the packages we have gotten to build properly while continuing to work on the problem packages. This repository is totally optional and was not needed with CentOS-6.2, but we recommend it be installed if you want to get your security updates as fast as possible.
Karanbir gets the credit for the new build system, called reimzul. It uses beanstalkd work queues and allows adding new builders to process the work as required.
The build system has the flexibility to allow us to import SRPMS into a git repo for packages we want to change, generate a new SRPM after edits for those packages, and submit those modified SRPMS into the work queues. It also allows for the submission of non-modified SRPMS directly without the need to import them into git. It automates several things that we have done in the past by hand (automatically knowing which packages are not built by CentOS (for example the RHN packages that deal with upstream subscriptions) and automatically copies multilib 32bit packages into the 64 bit tree. The system also reliably produces the Yum-Presto DeltaRPMS and metadata for minimizing download times for updates.
We do need to announce that CentOS-4 will be reaching the End Of Life at the end of February 2012. That means that there will be no more CentOS-4 updates after March 1st, 2012. If you are still using CentOS-4, you need to upgrade to CentOS-5 or CentOS-6 or switch to Red Hat's paid Extended Update Support for EL4 to continue to get updates. Please see the CentOS-4 EOL announcement for more details.
So, news on the CentOS front for 2012 is very promising and we are looking forward to great things in the new year.
Johnny, is the build system open source?
ReplyDeleteNo, the build system is not yet open source (or closed source for that matter, or anything else for that matter).
ReplyDeleteIt is right now a bunch of things all tied together with Bash scripts and Python scripts, etc.
It is certainly not in any state for anyone else to get benefit from it as it exists now.
We will not rule out getting it in a state where it can be released ... but no promises one way or another for now.
Congratulations for Karanbir, both for the baby and the build system.
ReplyDeleteMy worry is that it sounds like KB is the main (sole?) contributor to the build system and with a new baby on his hands the build system will fall behind again (I say this as a father of two - you just don't find time for such stuff unless it's your paying job and/or your partner is a full time parent) - unless it's dumped on github as-is to let others to tinker with it.
Not at all ... he built the build system and it is functional. Other developers have the ability to build packages using the build system. You will notice that Tru Huynh, Karanbir Singh, and I (Johnny Hughes) can all submit packages. We also have the ability to have others do it as well.
ReplyDeleteSo, these are 2 separate things ... the "infrastructure" of the build system. And the actual built packages for CentOS. We have more than one person who can use the build system ... we should not have any issues getting timely packages out of the build system.
Thanks for your response, Johnny.
DeleteI realize the Karanbir is not the sole contributor of CentOS packages.
What I was referring to is that future development of what you refer to as the "infrastructure" depends on Karanbir's availability, which I expect to be very limited and so are the chances of it ever being opened to the public.
That's why I request that you'll consider opening it up as it is now and let the public play with it.