On 03/09/2011 10:15 PM, William Warren wrote: > On 3/9/2011 11:44 AM, Karanbir Singh wrote: >> On 03/07/2011 10:48 PM, Karanbir Singh wrote: >>> and have the tree's over into QA. Once that is done, the updates can >>> churn though. >> Just a quick update to this, updates now churning. The last bits of 5.6 >> fell into place over the course of the last 24 hrs. >> > How about the updates that came out after 5.6 was released. Are you > going to roll those into the 5.6 tree directly or put out those updates > immediately after you roll out 5.6? We will always produce the OS tree to be an exact copy of our released media, with everything else in updates. Our media needs to be the exact same versions of programs as the upstream media to allow for 3rd party drivers to work properly at installation time. So, the answer is that versions newer than those on the upstream installation media for a given point release will always be placed in updates. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 253 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20110310/5514cf73/attachment-0007.sig>