2011/1/5 Karanbir Singh
<mail-lists@karan.org>
[...]
Couple of things worth clearing up:
CentOS is not SL
CentOS and SL target a very different Goal Set ( there is user end
overlap, which imho is good )
I know but the source is equal.
When we asked around for help from people, the *currnet* state of CentOS
was a bunch of srpms that needed to be looked at for content audits.
These srpms are widely available. What do you want to do with these
sources that would imply to you a beta or an alpha state ? as far as I
am concerned those sources represent the final product pretty much.
I'm seeking for two different things, one thing is an alpha or beta ISO (which gives you at least the ability to install a minimal CentOS 6) two check if procedures like Cobbler or Puppet or ... are still functional or if things need to be changed. Using SL6 or RHEL6 didn't help much because facter return different values (i.e. facter operatingsystem gives RedHat instead of CentOS which brake all operating system selectors).
The second thing is a built environment that help me to find bugs in the build process and gives me the ability to fix them. It would also be sufficient for me to only have the built environment to create my own ISOs and use them for testing (if there are too many concerns about offering alpha or beta ISO officially).
Can you quantify what you mean by 'open approach' ( basically, what
steps and what gains those steps would bring about )
See above, this is my motivation for having access to earlier releases where not everything is already compiling and working.
[...]
Problems remain where ? in CentOS or RHEL ? It was RHEL6 that had a
public beta, for issues that should have been reported against
bugzilla.r.c; or am I misunderstanding what you said ?
A bit, I mean problems remaining in the current CentOS 6 built process. I would like to help sorting problems out to get CentOS6 as soon as possible, but I don't know what problems are still blocking CentOS 6 from being ready to distribute. I checked the archives of the mailing lists as well as the website but didn't find things in this area. Maybe a link on the CentOS entry page: "Help making CentOS 6 ready to release" would be helpful.
Don't get me wrong, I am well aware of the fact that there are issues
and situations that need looking at and changing. But lets do the right
thing rather than just doing something. Going by the popularist current
mood of people on this list, I think people just want early access to a
codebase they can start using for their own use rather than actually
working towards building CentOS-6. Which makes me fear that the only way
we are going to get C6 out of the door in the next few weeks is by
clamping up, talking to the usual-suspects and just going back to the
CentOS-5 process. And to be honest, I don't really think these
conversations over the past two months have been wasted; but in the
grant scheme of things - getting 6.0 out of the door might be a better
target for now - as long as we can somehow agree that we get back to
this process engineering immediately after so as to not be in the same
situation, come 6.1.
Also, failback to the CentOS-5 process isn't necessarily a bad thing -
we know it works :)
I don't get you wrong (hopefully) and I really appreciate the work that is done from the CentOS team, I just want to figure out if there are possibilities to speed up the process to release CentOS 6 by helping with bug reports or patches to have CentOS 6 up in the air soon.
Kind regards, Thomas