On 06/17/2014 05:57 PM, Ljubomir Ljubojevic wrote: > On 06/17/2014 04:24 PM, Johnny Hughes wrote: >> On 06/17/2014 08:55 AM, Karanbir Singh wrote: >>> On 06/17/2014 02:10 PM, Ljubomir Ljubojevic wrote: >>>> On 06/16/2014 08:25 PM, Fabian Arrotin wrote: >>>>> As Karanbir announced it today, there will be "nightly builds" happening >>>>> every day, starting from today (the first one being scheduled to start >>>>> at 8PM UTC). >>>>> The whole process will be automated and would also start to reflect >>>>> those new trees. >>>>> That means that the url to enter for new network install, and yum >>>>> repositories will need to be using the 'latest' symlink when that one >>>>> will appear. (Normally full URL would be >>>>> http://buildlogs.centos.org/centos/7/os/x86_64-latest) >>>> It would be nice to have "-latest" URL ready for announcement purposes, >>>> so others know it will exist. >>>> >>>> >>> latest is something we want to do - its been spokean about as well, but >>> remember we are replacing rpms without a bump in Epoc:Version-Release, >>> so there is no way for yum etc to know that something has changed under it. >>> >>> hence, the only real testing path is to reinstall and re-evaluate newer >>> releases. >>> >>> - KB >>> >> >> I want to point out here for those who think this might look chaotic ... >> this process is very similar to what we have done only with our private >> QA team in the past. >> >> We would do these temporary tree pushes, etc. to the QA team and they >> would test, find issues, post the issues to bugs or the QA mailing list >> and we would fix. We have opened this up totally to the public to make >> the test group larger and hopefully find and fix issues faster, etc. >> >> However, the packages released here are going to do things LIKE ... be >> replaced with different builds that are newer with exactly the same EVR >> strings, etc. We may do other crazy things too. >> >> The bottom line is that these packages should ABSOLUTELY NOT be used on >> anything that is even slightly important .. although, you may be able to >> point to a newer repo and do something like "yum distro-sync full" to >> get all the new packages. >> >> That said, be careful with these packages and don't keep/use them except >> for this testing. Once we get a stabilized tree and that is released, >> then we can use that for real production things :) >> >> > > That is understood, at least by me. > > The reason I asked for this was that Youtube video emerged for people to > test C7 and Fabian posted message about "latest", so since I already > posted his message on Facebook and Google+ as a comment to Youtube > Install video, it would be nice to have (by tomorrow?) "latest" pointing > to last/only build so people do not start asking too many questions why > it is missing. > > And I will make sure to warn them about non-production, even tho I do > not think that will be the problem since those who want to try it only > want to look at it. > > might also want to make a note about distro-sync, that helps in this sort of a setup, massively. and also make sure people expire their yum repo configs in time -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc