[CentOS-devel] progress?

Sun Feb 20 17:30:35 UTC 2011
Fabian Arrotin <fabian.arrotin at arrfab.net>

On 02/20/2011 06:13 PM, Dag Wieers wrote:
>
> So it's absolutely normal a CentOS 5.6 release is 10 weeks late and
> there's no intent to speed up the process to lower the time to do future
> releases ?
>
> If that is the case, we might want to make that more clear on the wiki,
> eg. in my CentOS introduction presentation from 2008 we still mention that
> releases are (up to) 4 weeks behind RHEL.
>
> I don't think most of the users ever expected to be without security
> updates for 10 weeks or more when choosing CentOS, and that is an
> important characteristic.
>

Right, but as you said so in your multiple CentOS presentations, there 
are no warranty nor SLA on a delivery time : IIRC you explained that 
very clearly in the Pros/Cons slides between RHEL and CentOS ;-)

Working a little bit behind the scene and knowing the CentOS developers, 
i'm quite astonished that all the people complaining about the 'delay' 
always think about technical issues that CentOS developers have to deal 
with and not with their personal problems they have to deal with ... 
Until now i've *never* seen any comment like 'we hope that everything is 
ok on the family point-of-view' etc, etc ...
I don't think that the CentOS developers want to discuss what happens in 
their private life, nor the problems they have to deal with at $work, 
etc, etc ...

And on each release it's the same thread coming. It seems to me like a 
'chicken and eggs' problem : what has to be solved first ? people 
wanting a faster distro release or documenting it first ? Don't 
misunderstand me : i really would like to see the whole process 
documented and i think that some other members agree on that fact. (It 
seems SL team documents more what they are doing for example). But here 
is now a simple fact : consider how much time Johnny took to answer all 
the same questions (and even answered multiple times with the same 
answer) and so the time he couldn't spend on the build process itself ...

Fabian Arrotin