On 6/18/20 11:12 AM, Thomas Bendler wrote:> Hi Johnny, > > Am Mi., 17. Juni 2020 um 16:16 Uhr schrieb Johnny Hughes <johnny at centos.org >> : > >> [...] >> No one is trynig to make anything slower. >> > > This is good to hear but ... > >> [...] >> I can assure you .. I am working my butt off everyday to make CentOS >> Linux the best it can be. If you want to compare what the CentOS team >> (a small team) can do compared to Oracle (a tmulti billin dollar >> corporation who bought Sun Microsystems .. took over Java and Open >> Office, etc) .. well, we can not provide the resources they can provide. >> [...] > > > ... then I'm missing some kind of strategy on how to improve things (or > maybe I simply don't know they exist). Without having a detailed background > about the project setup and the way the small team works, I would at a > first glance assume that there are two options to improve. One would be to > make the team bigger (as you said, it's open and I'm pretty sure there are > enough volunteers) or a second one, by increasing the automation level for > the CentOS production. > > What do you think and are there discussions in the core CentOS community to > go either one of these routes? >While both of those would be helpful .. neither will really SOLVE the issue. This is an iterative process. You build something, test it, rebuild all the bad parts, test it again .. rinse, repeat We usually have the first build 3 or so days after they release. Many things build out of order. They get tested and rebuilt.> Regards Thomas >-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20200619/0cfbbc1e/attachment.sig>
On 6/19/20 10:18 AM, Johnny Hughes wrote:> On 6/18/20 11:12 AM, Thomas Bendler wrote: >> Hi Johnny, >> >> Am Mi., 17. Juni 2020 um 16:16 Uhr schrieb Johnny Hughes <johnny at centos.org >>> : >> >>> [...] >>> No one is trynig to make anything slower. >>> >> >> This is good to hear but ... >> >>> [...] >>> I can assure you .. I am working my butt off everyday to make CentOS >>> Linux the best it can be. If you want to compare what the CentOS team >>> (a small team) can do compared to Oracle (a tmulti billin dollar >>> corporation who bought Sun Microsystems .. took over Java and Open >>> Office, etc) .. well, we can not provide the resources they can provide. >>> [...] >> >> >> ... then I'm missing some kind of strategy on how to improve things (or >> maybe I simply don't know they exist). Without having a detailed background >> about the project setup and the way the small team works, I would at a >> first glance assume that there are two options to improve. One would be to >> make the team bigger (as you said, it's open and I'm pretty sure there are >> enough volunteers) or a second one, by increasing the automation level for >> the CentOS production. >> >> What do you think and are there discussions in the core CentOS community to >> go either one of these routes? >> > > While both of those would be helpful .. neither will really SOLVE the > issue. This is an iterative process. You build something, test it, > rebuild all the bad parts, test it again .. rinse, repeat > > We usually have the first build 3 or so days after they release. > > Many things build out of order. They get tested and rebuilt.How is this going to be fixed .. Welcome to CentOS Stream Stream will be , once it is fully implemented, the ACTUAL development of RHEL the 'next point release' on git.centos.org in the open. It will be a rolling distro that is GOING to be the Source Code used for next RHEL point release. Therefore, we will have all package as they are being worked on by the RHEL Engineers .. and you can see it happen in progress. You can also use it however you want. There will be no delay i this at all. It will be constantly moving. There will be no 500 pacakges drop or delays. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20200619/2b38ae0a/attachment.sig>
Le 19/06/2020 ? 17:29, Johnny Hughes a ?crit?:> How is this going to be fixed .. Welcome to CentOS Stream > > Stream will be , once it is fully implemented, the ACTUAL development of > RHEL the 'next point release' on git.centos.org in the open. > > It will be a rolling distro that is GOING to be the Source Code used for > next RHEL point release. > > Therefore, we will have all package as they are being worked on by the > RHEL Engineers .. and you can see it happen in progress. You can also > use it however you want. There will be no delay i this at all. It will > be constantly moving. There will be no 500 pacakges drop or delays.Reading this, I just want to say a big warm THANK YOU for churning out one of the finest Linux distributions. Keep up the good work. Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 Mob. : 06 51 80 12 12
On 20/06/20 3:29 am, Johnny Hughes wrote:> How is this going to be fixed .. Welcome to CentOS Stream > > Stream will be , once it is fully implemented, the ACTUAL development of > RHEL the 'next point release' on git.centos.org in the open.So basically stream is a testing ground for RHEL. It's not actually a rebuild of RHEL since it's what comes *before* RHEL, not after.> It will be a rolling distro that is GOING to be the Source Code used for > next RHEL point release. > > Therefore, we will have all package as they are being worked on by the > RHEL Engineers .. and you can see it happen in progress. You can also > use it however you want. There will be no delay i this at all. It will > be constantly moving. There will be no 500 pacakges drop or delays.This is all well and good, but I don't think that CentOS was ever meant to be a testing ground for RHEL. As the name actually stands for it is a "Community Enterprise OS" and it has always been a rebuild of the RHEL sources. Stream is basically RHEL Rolling Beta, and that can hardly be considered "Enterprise". I and I think many others find this focus on Stream to be rather distressing, and it does have the appearance to be taking focus away from the core OS. This is further evidenced by the long wait times for release. The way I see it, Red Hat pays the bills now, Red Hat employs the core team, and Red Hat wants a RHEL Beta platform, so that is what they have decreed that CentOS will become. Now I could be wrong here because I certainly don't have any inside information about this, but it seems from teh outside looking in that any progress on the core OS is incidental and time spent on it has to be time leftover after any work is done on Stream. Now I don't have an issue with Stream, in fact I think taht Stream can be beneficial to CentOS, but it hsould not be at the expense of the core OS, imo. The core OS should take priority over any other CentOS project, whether it be streams, or SIGs or anything else, because we can't really have a Community Enterprise OS without the core OS. Peter