I do appreciate everyone's efforts! <div><br></div><div>I have a few idle servers locally that can be used for compiling, but unfortunately cannot make the servers accessible to the outside. If that helps, I am willing to toss in CPU cycles.<br>
<br><div class="gmail_quote">On Thu, Feb 24, 2011 at 12:11 PM, Johnny Hughes <span dir="ltr"><<a href="mailto:johnny@centos.org">johnny@centos.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 02/24/2011 10:59 AM, Thomas Bendler wrote:<br>
> 2011/2/23 Karanbir Singh <<a href="mailto:mail-lists@karan.org">mail-lists@karan.org</a><br>
</div>> <mailto:<a href="mailto:mail-lists@karan.org">mail-lists@karan.org</a>>><br>
<div><div></div><div class="h5">><br>
> On 02/22/2011 08:26 PM, Thomas Bendler wrote:<br>
> > And to make my point clear, I don't believe it is rocket science to<br>
> > get such a release cycle established if _more_ skilled people are<br>
> > involved in the release creation (beyond translation work).<br>
> I do believe you dont know what you are talking about, have done no<br>
> research or aware of the CentOS process. You seem to be going on and on<br>
> about getting more eyes on the ball, which is exactly what we attempted<br>
> to do last year, and the option is still open.<br>
><br>
><br>
> Funny to know that I don't know what I'm talking about but maybe you can<br>
> be more specific. As I already pointed out in another mail, for me it<br>
> look like that having more than one release at the same time (4.9, 5.6<br>
> and 6) result in a major slow down of release cycle time. This means for<br>
> me, the project isn't able to scale (correct me if I'm wrong). When the<br>
> project can't scale it is under normal circumstances a matter of human<br>
> resources or technical boundaries. As you told me already in December,<br>
> it is not a technical problem. So from my point of view it could _only_<br>
> be a matter of human resources in terms that not enough people working<br>
> on the release (again, correct me if I'm wrong). To offer my help I<br>
> asked already in December, please provide a list of packages that don't<br>
> compile so that people that are willing to help can help getting this<br>
> packages compiled (i.e. with differnet mock settings or whatever needed<br>
> to get this compiled). If the recompile isn't possible because the SRPM<br>
> is broken they can submit Bugreports to RH. But I only saw such a list<br>
> on the SL website<br>
> (<a href="https://www.scientificlinux.org/distributions/6x/build/problembyrpm" target="_blank">https://www.scientificlinux.org/distributions/6x/build/problembyrpm</a>),<br>
> not on the CentOS website.<br>
><br>
> What I heard in the meantime is that CentOS has a policy that the next<br>
> release must be compiled with CentOS what I think is a bit funny simply<br>
> because RedHat don't use a build environment based in RedHat (I read an<br>
> article in the press indicating that they use FC12 koji with some FC13,<br>
> FC14 backports, but I can't proof this). But the point is still, if you<br>
> and your team allow skilled people to support you in the release<br>
> creation (not by signing packages or so, but to work out open items,<br>
> problems, whatsoever) it is something that the CentOS project will<br>
> benefit, specially if you look at the mails currently on the list, most<br>
> mails are from the same type, when is CentOS X.X released and why isn't<br>
> it already released.<br>
<br>
</div></div>Why isn't SL released yet ... why did Oracle only release it last week<br>
... because it takes time and it is hard.<br>
<br>
If you want to use CentOS, feel free to use it. If you don't, feel free<br>
to leave.<br>
<br>
<br>_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
<br></blockquote></div><br></div>