Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
First of all, I want to ask that you be patient with us. Changing the way that the hundreds of people on the RHEL team do their work is going to take time. Developing the tooling to make everything work perfectly, and in an automated fashion, is also going to take time. And some of the things that were proposed to the Board will end up changing, based on what doesn’t work, and on the feedback from you, the CentOS community, as well as Red Hat’s customers and partners.
A central point of discussion was ensuring transparency. We want to move the RHEL development more into the public, and CentOS Stream is the cornerstone of that.
CentOS Stream will be a rolling preview of what is happening in RHEL development. This will allow you to experiment with the next version before it releases, and ensure that what you are working on will work, day one, when the next minor release of RHEL is announced.
SIGs, too, will be able to build and test against this preview, so that when the next minor release comes out, there will be no surprises.
We are working on a FAQ to answer what we anticipate will be at the top of everyone’s mind, but I’ll address a few questions that we’re already receiving.
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
Q: How can I contribute changes? A: This is still being worked on, and we ask for your patience as we work towards this. This is indeed a goal, but getting the stream itself working perfectly must happen first. Meanwhile, we’re working with the RHEL engineering team on a process where contributions from the community can be considered as part of their regular development workflow. The last thing we want is to set an expectation that we cannot meet, so we want to ensure that we have a workable process before we start asking you for contributions.
We encourage your further questions, and look forward to figuring out with you how to make CentOS Stream successful for all constituents.
On Tue, Oct 8, 2019, at 11:37 AM, Rich Bowen wrote:
Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
Great! Was this a public or invite-only meeting? (I didn't see anything in my mail archives announcing it.)
First of all, I want to ask that you be patient with us. Changing the way that the hundreds of people on the RHEL team do their work is going to take time. Developing the tooling to make everything work perfectly, and in an automated fashion, is also going to take time. And some of the things that were proposed to the Board will end up changing, based on what doesn’t work, and on the feedback from you, the CentOS community, as well as Red Hat’s customers and partners.
A central point of discussion was ensuring transparency. We want to move the RHEL development more into the public, and CentOS Stream is the cornerstone of that.
CentOS Stream will be a rolling preview of what is happening in RHEL development. This will allow you to experiment with the next version before it releases, and ensure that what you are working on will work, day one, when the next minor release of RHEL is announced.
The increased transparency is greatly appreciated and is especially reassuring in light of the IBM acquisition.
SIGs, too, will be able to build and test against this preview, so that when the next minor release comes out, there will be no surprises.
We are working on a FAQ to answer what we anticipate will be at the top of everyone’s mind, but I’ll address a few questions that we’re already receiving.
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
Q: How can I contribute changes? A: This is still being worked on, and we ask for your patience as we work towards this. This is indeed a goal, but getting the stream itself working perfectly must happen first. Meanwhile, we’re working with the RHEL engineering team on a process where contributions from the community can be considered as part of their regular development workflow. The last thing we want is to set an expectation that we cannot meet, so we want to ensure that we have a workable process before we start asking you for contributions.
We encourage your further questions, and look forward to figuring out with you how to make CentOS Stream successful for all constituents.
I look forward to the further details as they become available.
V/r, James Cassell
-- Rich Bowen: CentOS Community Manager rbowen@redhat.com @rbowen // @CentOSProject 1 859 351 9166
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 10/8/19 11:46 AM, James Cassell wrote:
On Tue, Oct 8, 2019, at 11:37 AM, Rich Bowen wrote:
Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
Great! Was this a public or invite-only meeting? (I didn't see anything in my mail archives announcing it.)
This meeting was an internal RH meeting to sort out some of the internal-to-redhat pieces, but we're working from a policy of being as open and transparent about it as possible.
First of all, I want to ask that you be patient with us. Changing the way that the hundreds of people on the RHEL team do their work is going to take time. Developing the tooling to make everything work perfectly, and in an automated fashion, is also going to take time. And some of the things that were proposed to the Board will end up changing, based on what doesn’t work, and on the feedback from you, the CentOS community, as well as Red Hat’s customers and partners.
A central point of discussion was ensuring transparency. We want to move the RHEL development more into the public, and CentOS Stream is the cornerstone of that.
CentOS Stream will be a rolling preview of what is happening in RHEL development. This will allow you to experiment with the next version before it releases, and ensure that what you are working on will work, day one, when the next minor release of RHEL is announced.
The increased transparency is greatly appreciated and is especially reassuring in light of the IBM acquisition.
Glad to hear.
SIGs, too, will be able to build and test against this preview, so that when the next minor release comes out, there will be no surprises.
We are working on a FAQ to answer what we anticipate will be at the top of everyone’s mind, but I’ll address a few questions that we’re already receiving.
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
Q: How can I contribute changes? A: This is still being worked on, and we ask for your patience as we work towards this. This is indeed a goal, but getting the stream itself working perfectly must happen first. Meanwhile, we’re working with the RHEL engineering team on a process where contributions from the community can be considered as part of their regular development workflow. The last thing we want is to set an expectation that we cannot meet, so we want to ensure that we have a workable process before we start asking you for contributions.
We encourage your further questions, and look forward to figuring out with you how to make CentOS Stream successful for all constituents.
I look forward to the further details as they become available.
We'll be open about what we're working on, but I do want to point out that for some of this will only be "we're sorting out internal RH policy" or whatever.
On Tue, Oct 8, 2019 at 12:57 PM Jim Perrin jperrin@centos.org wrote:
On 10/8/19 11:46 AM, James Cassell wrote:
On Tue, Oct 8, 2019, at 11:37 AM, Rich Bowen wrote:
Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
Great! Was this a public or invite-only meeting? (I didn't see anything in my mail archives announcing it.)
This meeting was an internal RH meeting to sort out some of the internal-to-redhat pieces, but we're working from a policy of being as open and transparent about it as possible.
Then we already have something to be worried about. The meeting wasn't open, wasn't announced to the public, and the attendees and content of the meeting is unavailable to the public. Not a good start to a "transparent as possible" process.
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
This implies that development of new features or backported features for RHEL 8 will end as soon as RHEL 9 is released. That is.... likely to be a problem.
Q: How can I contribute changes? A: This is still being worked on, and we ask for your patience as we work towards this. This is indeed a goal, but getting the stream itself working perfectly must happen first. Meanwhile, we’re working with the RHEL engineering team on a process where contributions from the community can be considered as part of their regular development workflow. The last thing we want is to set an expectation that we cannot meet, so we want to ensure that we have a workable process before we start asking you for contributions.
We encourage your further questions, and look forward to figuring out with you how to make CentOS Stream successful for all constituents.
I look forward to the further details as they become available.
We'll be open about what we're working on, but I do want to point out that for some of this will only be "we're sorting out internal RH policy" or whatever.
We just saw this sort of thing play out with the release of the python3 for RHEL 7.7. It would have been nice to see those in a "Stream" channel, if this is going to be the way major features get rolled out.
On 10/9/19 8:19 AM, Nico Kadel-Garcia wrote:
This meeting was an internal RH meeting to sort out some of the internal-to-redhat pieces, but we're working from a policy of being as open and transparent about it as possible.
Then we already have something to be worried about. The meeting wasn't open, wasn't announced to the public, and the attendees and content of the meeting is unavailable to the public. Not a good start to a "transparent as possible" process.
Red Hat is a business. There are a lot of meetings at Red Hat to which you are not invited, and for which you will not receive minutes. The purpose of this email was to inform the community about those decisions that effect the community. That is what "transparent as possible" means - not that Red Hat intends to conduct all of their meetings in public.
On 10/9/19 8:19 AM, Nico Kadel-Garcia wrote:
On Tue, Oct 8, 2019 at 12:57 PM Jim Perrin jperrin@centos.org wrote:
On 10/8/19 11:46 AM, James Cassell wrote:
On Tue, Oct 8, 2019, at 11:37 AM, Rich Bowen wrote:
Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
Great! Was this a public or invite-only meeting? (I didn't see anything in my mail archives announcing it.)
This meeting was an internal RH meeting to sort out some of the internal-to-redhat pieces, but we're working from a policy of being as open and transparent about it as possible.
Then we already have something to be worried about. The meeting wasn't open, wasn't announced to the public, and the attendees and content of the meeting is unavailable to the public. Not a good start to a "transparent as possible" process.
Quite the opposite actually. Most of this meeting dealt with internal policy, which is something companies don't realistically share. Rich's email covered it well.
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
This implies that development of new features or backported features for RHEL 8 will end as soon as RHEL 9 is released. That is.... likely to be a problem.
It implies that RH would like the community to focus on the latest release rather than previous iterations, nothing more nefarious than that.
Q: How can I contribute changes? A: This is still being worked on, and we ask for your patience as we work towards this. This is indeed a goal, but getting the stream itself working perfectly must happen first. Meanwhile, we’re working with the RHEL engineering team on a process where contributions from the community can be considered as part of their regular development workflow. The last thing we want is to set an expectation that we cannot meet, so we want to ensure that we have a workable process before we start asking you for contributions.
We encourage your further questions, and look forward to figuring out with you how to make CentOS Stream successful for all constituents.
I look forward to the further details as they become available.
We'll be open about what we're working on, but I do want to point out that for some of this will only be "we're sorting out internal RH policy" or whatever.
We just saw this sort of thing play out with the release of the python3 for RHEL 7.7. It would have been nice to see those in a "Stream" channel, if this is going to be the way major features get rolled out.
This is the sort of thing you could expect from Stream, yes.
On 08/10/2019 18:57, Jim Perrin wrote:
On 10/8/19 11:46 AM, James Cassell wrote:
On Tue, Oct 8, 2019, at 11:37 AM, Rich Bowen wrote:
Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
Is there any update on this topic?
For the OpsTools SIG, I'd like to build packages to be consumed in OpenStack Kolla; the same is true for the Messaging SIG; the output should flow into the Cloud SIG and also into the OpsTools SIG.
That also impacts work upstream.
Is there any timeline (if existent?) or anything else on progress you could share here?
Thank you, Matthias
Thanks for the update Rich, I just want to raise one point that might not have been considered.
On 10/8/19 08:37, Rich Bowen wrote:
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
To quote from earlier in your email "This will allow you to experiment with the next version before it releases, and ensure that what you are working on will work, day one, when the next minor release of RHEL is announced. SIGs, too, will be able to build and test against this preview, so that when the next minor release comes out, there will be no surprises"
I'm somewhat surprised by the plan to stop the 8 Stream, once the 9 Stream starts up. Even once the work on a future major version starts, there are still minor releases happening on the released version, which come with noteworthy changes and updates, e.g. 7.7 just got released a few months back, when the 8 beta was out. 7.7 included numerous changes and new features, drivers and improvements (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...). I'm guessing that development for RedHat 8 has been more than a year in the works!
I appreciate that you do tend to limit the scope a bit more with the later point releases, but stopping the Stream at that point seems like it would go completely against the intent declared earlier, because at least based on past RedHat development and release approaches, there will be RHEL 8 minor releases still coming out with notable changes more than a year after development work on RHEL 9 would have started.
Paul
Hi Folks,
On 10/8/19 6:17 PM, Paul Graydon wrote:
I'm somewhat surprised by the plan to stop the 8 Stream, once the 9 Stream starts up. Even once the work on a future major version starts, there are still minor releases happening on the released version, which come with noteworthy changes and updates, e.g. 7.7 just got released a few months back, when the 8 beta was out. 7.7 included numerous changes and new features, drivers and improvements (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...). I'm guessing that development for RedHat 8 has been more than a year in the works!
To echo this concern as well. I am a bit surprise that if CentOS Stream becomes upstream, it will be stopped before the end of the release cycle.
However maybe it make sense to align to the RHEL lifecycle [1], and decide that CentOS don't do Stream for "Maintenace Support 2" and beyond, where new functionalities and updates are limited.
The most important question is for CentOS 8. What happens when CentOS Stream "8" switch to upstream "9" ? Business as usual and we continue to rebuild all updates from git.centos.org ?
It is very important to clarify this point, as it will shape how we can use CentOS for the future.
On 10/9/19 3:12 AM, Thomas Oulevey wrote:
Hi Folks,
On 10/8/19 6:17 PM, Paul Graydon wrote:
I'm somewhat surprised by the plan to stop the 8 Stream, once the 9 Stream starts up. Even once the work on a future major version starts, there are still minor releases happening on the released version, which come with noteworthy changes and updates, e.g. 7.7 just got released a few months back, when the 8 beta was out. 7.7 included numerous changes and new features, drivers and improvements (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/htm...). I'm guessing that development for RedHat 8 has been more than a year in the works!
To echo this concern as well. I am a bit surprise that if CentOS Stream becomes upstream, it will be stopped before the end of the release cycle.
However maybe it make sense to align to the RHEL lifecycle [1], and decide that CentOS don't do Stream for "Maintenace Support 2" and beyond, where new functionalities and updates are limited.
This concern has come up elsewhere as well. It might help to frame this as an experiment. Right now, RH isn't really sure how this will work, so we need to build it, and begin getting metrics around usage, feedback and community involvement. That will help shape what happens in the future.
The most important question is for CentOS 8. What happens when CentOS Stream "8" switch to upstream "9" ? Business as usual and we continue to rebuild all updates from git.centos.org ?
It is very important to clarify this point, as it will shape how we can use CentOS for the future.
There are no changes to CentOS Linux as a part of the Stream release. Could you please clarify your concern here to help me understand it better?
Hi Jim,
On 10/9/19 3:02 PM, Jim Perrin wrote:
The most important question is for CentOS 8. What happens when CentOS Stream "8" switch to upstream "9" ? Business as usual and we continue to rebuild all updates from git.centos.org ?
It is very important to clarify this point, as it will shape how we can use CentOS for the future.
There are no changes to CentOS Linux as a part of the Stream release. Could you please clarify your concern here to help me understand it better?
I just wanted to be sure that what happens to CentOS 8 Stream, doesn't affect CentOS 8 rebuild as we know it.
Thanks for the clarification.
On Wed, Oct 9, 2019 at 8:07 AM Thomas Oulevey thomas.oulevey@cern.ch wrote:
Hi Jim,
On 10/9/19 3:02 PM, Jim Perrin wrote:
The most important question is for CentOS 8. What happens when CentOS Stream "8" switch to upstream "9" ? Business as usual and we continue to rebuild all updates from git.centos.org ?
It is very important to clarify this point, as it will shape how we can use CentOS for the future.
There are no changes to CentOS Linux as a part of the Stream release. Could you please clarify your concern here to help me understand it
better?
I just wanted to be sure that what happens to CentOS 8 Stream, doesn't affect CentOS 8 rebuild as we know it.
Thanks for the clarification.
We have no plans to change the CentOS 8 rebuild and the way Jim and the team are building CentOS Stream and the rebuild is smart and keeps them fairly separate from each other so accidents should be rare if ever.
-Mike
-- Thomas Oulevey _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 10/9/19 4:14 PM, Mike McGrath wrote:
On Wed, Oct 9, 2019 at 8:07 AM Thomas Oulevey <thomas.oulevey@cern.ch mailto:thomas.oulevey@cern.ch> wrote:
Hi Jim, On 10/9/19 3:02 PM, Jim Perrin wrote: >> The most important question is for CentOS 8. What happens when CentOS >> Stream "8" switch to upstream "9" ? >> Business as usual and we continue to rebuild all updates from >> git.centos.org <http://git.centos.org> ? >> >> It is very important to clarify this point, as it will shape how we >> can use CentOS for the future. >> > > There are no changes to CentOS Linux as a part of the Stream release. > Could you please clarify your concern here to help me understand it better? > > I just wanted to be sure that what happens to CentOS 8 Stream, doesn't affect CentOS 8 rebuild as we know it. Thanks for the clarification.We have no plans to change the CentOS 8 rebuild and the way Jim and the team are building CentOS Stream and the rebuild is smart and keeps them fairly separate from each other so accidents should be rare if ever.
-Mike
If Stream was named something like "CentOS Next Upstream", the people would not be confused in what is the intention. Most think changes will be for CentOS, not RHEL.
-- Thomas Oulevey _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org <mailto:CentOS-devel@centos.org> https://lists.centos.org/mailman/listinfo/centos-devel--
Mike McGrath
Platform Engineering - Chicago
Red Hat
mmcgrath@redhat.com mailto:mmcgrath@redhat.com T: (312)-660-3547 tel:(312)-660-3547
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
My one concern with all of this is the use of the name "CentOS Streams". Where this is actually the "Enterprise Linux Streams", I feel calling it "CentOS Streams" will cause confusion with CentOS 8 and beyond. The first example would be in these mailing lists, while trying to help troubleshoot an issue, I can easily see this happening... "What version of CentOS are you running?" : "8." : "Wow, that's odd, I don't even see that kernel version as an option for CentOS 8". Could we not call it "EL Streams" so it still has the proper association to CentOS/RHEL as the upstream build, but reduces the confusion with the much further downstream LTS versions of CentOS?
Gregory Young
-----Original Message----- From: CentOS-devel centos-devel-bounces@centos.org On Behalf Of Rich Bowen Sent: October 8, 2019 11:38 AM To: The CentOS developers mailing list. centos-devel@centos.org Subject: [CentOS-devel] CentOS stream meeting - update
Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
First of all, I want to ask that you be patient with us. Changing the way that the hundreds of people on the RHEL team do their work is going to take time. Developing the tooling to make everything work perfectly, and in an automated fashion, is also going to take time. And some of the things that were proposed to the Board will end up changing, based on what doesn’t work, and on the feedback from you, the CentOS community, as well as Red Hat’s customers and partners.
A central point of discussion was ensuring transparency. We want to move the RHEL development more into the public, and CentOS Stream is the cornerstone of that.
CentOS Stream will be a rolling preview of what is happening in RHEL development. This will allow you to experiment with the next version before it releases, and ensure that what you are working on will work, day one, when the next minor release of RHEL is announced.
SIGs, too, will be able to build and test against this preview, so that when the next minor release comes out, there will be no surprises.
We are working on a FAQ to answer what we anticipate will be at the top of everyone’s mind, but I’ll address a few questions that we’re already receiving.
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
Q: How can I contribute changes? A: This is still being worked on, and we ask for your patience as we work towards this. This is indeed a goal, but getting the stream itself working perfectly must happen first. Meanwhile, we’re working with the RHEL engineering team on a process where contributions from the community can be considered as part of their regular development workflow. The last thing we want is to set an expectation that we cannot meet, so we want to ensure that we have a workable process before we start asking you for contributions.
We encourage your further questions, and look forward to figuring out with you how to make CentOS Stream successful for all constituents.
-- Rich Bowen: CentOS Community Manager rbowen@redhat.com @rbowen // @CentOSProject 1 859 351 9166
_______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 10/8/19 12:45 PM, Young, Gregory wrote:
My one concern with all of this is the use of the name "CentOS Streams". Where this is actually the "Enterprise Linux Streams", I feel calling it "CentOS Streams" will cause confusion with CentOS 8 and beyond. The first example would be in these mailing lists, while trying to help troubleshoot an issue, I can easily see this happening... "What version of CentOS are you running?" : "8." : "Wow, that's odd, I don't even see that kernel version as an option for CentOS 8". Could we not call it "EL Streams" so it still has the proper association to CentOS/RHEL as the upstream build, but reduces the confusion with the much further downstream LTS versions of CentOS?
Naming is always hard. CentOS Stream is an output of the CentOS Project, and, thus the name. I am sure that we can find ways to disambiguate. I would suggest that the correct answer to the above hypothetical question is that the version you're running is Stream 8, not 8.
-----Original Message----- From: CentOS-devel centos-devel-bounces@centos.org On Behalf Of Rich Bowen Sent: October 8, 2019 11:38 AM To: The CentOS developers mailing list. centos-devel@centos.org Subject: [CentOS-devel] CentOS stream meeting - update
Last week a group of Red Hat engineers, management, and members of the CentOS and Fedora communities, met at the Red Hat office in Boston to discuss how to implement CentOS Stream and formally kick-off the project, which, as you are aware, was announced the week before. Many details that were omitted in the original announcement were debated, and we came to an agreement on much, but not all, of these things.
First of all, I want to ask that you be patient with us. Changing the way that the hundreds of people on the RHEL team do their work is going to take time. Developing the tooling to make everything work perfectly, and in an automated fashion, is also going to take time. And some of the things that were proposed to the Board will end up changing, based on what doesn’t work, and on the feedback from you, the CentOS community, as well as Red Hat’s customers and partners.
A central point of discussion was ensuring transparency. We want to move the RHEL development more into the public, and CentOS Stream is the cornerstone of that.
CentOS Stream will be a rolling preview of what is happening in RHEL development. This will allow you to experiment with the next version before it releases, and ensure that what you are working on will work, day one, when the next minor release of RHEL is announced.
SIGs, too, will be able to build and test against this preview, so that when the next minor release comes out, there will be no surprises.
We are working on a FAQ to answer what we anticipate will be at the top of everyone’s mind, but I’ll address a few questions that we’re already receiving.
Q: How many streams will there be? Will there be a stream for 8 and another for 9? A: When the development for RHEL 9 begins, the stream for 8 will end. We plan to have a one-year overlap, to allow for transition from one stream to the other. But we do not intend to keep the 8 Stream going for the entirety of the RHEL 8 support window.
Q: How can I contribute changes? A: This is still being worked on, and we ask for your patience as we work towards this. This is indeed a goal, but getting the stream itself working perfectly must happen first. Meanwhile, we’re working with the RHEL engineering team on a process where contributions from the community can be considered as part of their regular development workflow. The last thing we want is to set an expectation that we cannot meet, so we want to ensure that we have a workable process before we start asking you for contributions.
We encourage your further questions, and look forward to figuring out with you how to make CentOS Stream successful for all constituents.
-- Rich Bowen: CentOS Community Manager rbowen@redhat.com @rbowen // @CentOSProject 1 859 351 9166
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-
James Cassell -
Jim Perrin -
Ljubomir Ljubojevic -
Matthias Runge -
Mike McGrath -
Nico Kadel-Garcia -
Paul Graydon -
Rich Bowen -
Thomas Oulevey -
Young, Gregory