Sender: |
|
Date: |
Wed, 18 Jul 2012 13:34:55 +0100 |
Reply-To: |
|
Content-Transfer-Encoding: |
7bit |
Subject: |
|
From: |
|
Content-Type: |
text/plain; charset=ISO-8859-1 |
In-Reply-To: |
|
MIME-Version: |
1.0 |
Comments: |
|
Parts/Attachments: |
|
|
Hi,
On 07/11/2012 03:44 AM, Nico Kadel-Garcia wrote:
> I'm perhaps being unclear, An announcemenbt that goes out at the same
> time as the release itself is not helpful. They've selected as a
Mirrors know about the upcoming release well in advance - remember that
we seed in excess of 1200 external non .centos.org mirrors before a
release. We, CentOS, 'announce' when users can do a yum update. If you
follow any of the routes where upcoming release work is being
documented, you would have known about the upcoming release well in advance.
> matter of policy not to announce pending releases: it drove me nuts,
> and and is one of the contributing reasons to my switch to Scientific
> Linux.
> Scientific Linux's very effective "rolling" updates for components,
> before a new release is published, has been very, very helpful to me
> in my personal research work building new packages. I'm not doing a
> panicky, unplanned rebuild of my packages for what is an unplanned and
> unexpected release with hundreds of updated components: I can keep my
> testing environments up to date before the release.
So, run a staged local repo, and dont deploy from upstream to production
on the fly. Its what pretty much everyone does.
- KB
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax
GnuPG Key : http://www.karan.org/publickey.asc
|
|
|