Carlos Rodriguez-Fernandez wrote:
> After much discussion, the AlmaLinux OS Foundation board today has
> decided to drop the aim to be 1:1 with RHEL. AlmaLinux OS will instead
> aim to be Application Binary Interface (ABI) compatible*
So this is now a significant difference between AlmaLinux and
On 7/14/23 00:02, Vitaly Zaitsev via devel wrote:
On 14/07/2023 08:16, Carlos Rodriguez-Fernandez wrote:
After much discussion, the AlmaLinux OS Foundation board today has
decided to drop the aim to be 1:1 with RHEL. AlmaLinux OS will instead
aim to be Application Binary Interface (ABI)
On 14/07/2023 08:16, Carlos Rodriguez-Fernandez wrote:
After much discussion, the AlmaLinux OS Foundation board today has
decided to drop the aim to be 1:1 with RHEL. AlmaLinux OS will instead
aim to be Application Binary Interface (ABI) compatible*
Imagine Red Hat shutting down CentOS Stream
This is actually good news, especially for the CentOS Stream project.
https://almalinux.org/blog/future-of-almalinux/
Quotes:
After much discussion, the AlmaLinux OS Foundation board today has
decided to drop the aim to be 1:1 with RHEL. AlmaLinux OS will instead
aim to be Application
SUSE has also jumped in to say they will provide an alternative, but compatible
Linux to RH.
Leslie Satenstein
On Tuesday, July 11, 2023 at 06:49:38 a.m. GMT-4, Kevin Kofler via devel
wrote:
Oracle has (finally – the community projects Rocky and Alma were much
quicker to
On Tue, Jul 11 2023 at 09:18:57 PM +0200, Leon Fauster via devel
wrote:
C8S ends 2024, while RHEL8 ends 2029
C9S ends 2027, while RHEL9 ends 2032
You're forgetting the Extended life cycle support phase. RHEL 8 and 9
will both have a 13-year lifecycle (down from 14 years). See this table:
Am 11.07.23 um 21:02 schrieb Chris Adams:
Once upon a time, Mattia Verga said:
Since RHEL is made out from Centos Stream and Centos Stream is made out from
Fedora ELN, can't Alma and Rocky branch directly from Fedora?
Can we collaborate in some way with those communities so that we support
Once upon a time, Mattia Verga said:
> Since RHEL is made out from Centos Stream and Centos Stream is made out from
> Fedora ELN, can't Alma and Rocky branch directly from Fedora?
> Can we collaborate in some way with those communities so that we support each
> other? I mean, like we have
Den tis 11 juli 2023 kl 19:12 skrev Mattia Verga via devel <
devel@lists.fedoraproject.org>:
> Since RHEL is made out from Centos Stream and Centos Stream is made out
> from Fedora ELN, can't Alma and Rocky branch directly from Fedora?
>
Can we collaborate in some way with those communities so
Since RHEL is made out from Centos Stream and Centos Stream is made out from
Fedora ELN, can't Alma and Rocky branch directly from Fedora?
Can we collaborate in some way with those communities so that we support each
other? I mean, like we have Fedora ELN and EPEL...
Inviato da Proton Mail
Kevin Kofler via devel venit, vidit, dixit 2023-07-11 12:49:10:
> Oracle has (finally – the community projects Rocky and Alma were much
> quicker to react) made an announcement about the situation:
> https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/
Thanks for
Den tis 11 juli 2023 kl 12:49 skrev Kevin Kofler via devel <
devel@lists.fedoraproject.org>:
> Oracle has (finally – the community projects Rocky and Alma were much
> quicker to react) made an announcement about the situation:
>
>
On Tue, Jul 11, 2023 at 12:49:10PM +0200, Kevin Kofler via devel wrote:
> Oracle has (finally – the community projects Rocky and Alma were much
> quicker to react) made an announcement about the situation:
> https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/
SUSE
Oracle has (finally – the community projects Rocky and Alma were much
quicker to react) made an announcement about the situation:
https://www.oracle.com/news/announcement/blog/keep-linux-open-and-free-2023-07-10/
Kevin Kofler
___
devel mailing
Am 03.07.23 um 02:00 schrieb Michael Catanzaro:
On Sun, Jul 2 2023 at 06:27:48 PM -0400, Demi Marie Obenour
wrote:
What about stuff that is too urgent to wait on Red Hat QA? There have
been vulnerabilities (such as CVE-2013-0156 and Log4Shell) for which
unauthenticated, fully automated,
On Sun, Jul 2 2023 at 06:27:48 PM -0400, Demi Marie Obenour
wrote:
What about stuff that is too urgent to wait on Red Hat QA? There have
been vulnerabilities (such as CVE-2013-0156 and Log4Shell) for which
unauthenticated, fully automated, remote code execution exploits have
been found very,
On 6/24/23 11:05, Michael Catanzaro wrote:
>
> On Sat, Jun 24 2023 at 08:53:32 AM -0500, Chris Adams
> wrote:
>>> Is it? At one point, there were considerable gaps in security
>>> updates;
>> RHEL 9.x would get an update while CentOS Stream 9 (as the target for
>> RHEL 9.[x+1]) didn't get a
On Sun, Jul 2 2023 at 09:53:30 PM +, "Smith, Stewart via devel"
wrote:
With this development model, what is the thought for those who may
want to / be able to submit pull requests to CentOS Stream with
security fixes?
It really depends. CentOS Stream does accept merge requests. With
On Jun 24, 2023, at 8:05 AM, Michael Catanzaro wrote:
>
> On Sat, Jun 24 2023 at 08:53:32 AM -0500, Chris Adams
> wrote:
>>> Is it? At one point, there were considerable gaps in security
>>> updates;
>> RHEL 9.x would get an update while CentOS Stream 9 (as the target for
>> RHEL 9.[x+1])
> On Jun 22, 2023, at 2:01 AM, Matthew Miller wrote:
>>
>>>
>>> ELN is a build of (some) Fedora packages with EL-specific options, so
>>> it requires Fedora.
>> ELN can exist off an internal non fedora tree. Just depends who is
>> updating the tree.
>
> Sure, but... that's the _opposite_ of
Neal Gompa wrote:
> I will also point out that CentOS Stream is perfectly suitable for
> production use, and I would argue it provides a differentiated
> experience in its own right: because CentOS Stream does not go through
> certification work that locks on specific package versions, any and
>
Hi Leon,
> On 24. Jun 2023, at 19:44, Leon Fauster via devel
> wrote:
>
>> I will also point out that CentOS Stream is perfectly suitable for
>> production use, and I would argue it provides a differentiated
>
> Nope, its not perfect for production use. Just an example of _many_:
>
>
On 2023-06-25 14:29, Dominik 'Rathann' Mierzejewski wrote:
The FOSS licenses give you the right to share the SRPMS, sans the Red
Hat trademarks.
The GPL, specifically, might guarantee that right, but not all of the
distribution is under the terms of the GPL. I don't have a license
count
On Sunday, 25 June 2023 at 02:44, Kevin Kofler via devel wrote:
> Neal Gompa wrote:
>
> > On Fri, Jun 23, 2023 at 6:09 PM Kevin Kofler via devel wrote:
> >>
> >> Josh Boyer wrote:
> >> > Agree with Matthew fully here. We've been working rather hard
> >> > internally to adjust the development
Neal Gompa wrote:
> On Fri, Jun 23, 2023 at 6:09 PM Kevin Kofler via devel wrote:
>>
>> Josh Boyer wrote:
>> > Agree with Matthew fully here. We've been working rather hard
>> > internally to adjust the development process for RHEL to be more
>> > collaborative and open than it ever has before.
On 2023-06-24 06:53, Chris Adams wrote:
Once upon a time, Neal Gompa said:
I will also point out that CentOS Stream is perfectly suitable for
production use
Is it? At one point, there were considerable gaps in security updates;
CentOS delayed security updates for 6-8 weeks, twice a year,
I do have packages on a RHEL9 system that do not appear in
https://kojihub.stream.centos.org/koji/ - so the fix is unknown from an
external view
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Once upon a time, Aleksandra Fedorova said:
> In this case you don't need a repo, you need just this specific build to
> apply it on your environment, isn't it?
If I only had one system to worry about, maybe (although maybe not, if
the build introduces a new dependency for example). But if I
> I will also point out that CentOS Stream is perfectly suitable for
> production use, and I would argue it provides a differentiated
Nope, its not perfect for production use. Just an example of _many_:
https://bugzilla.redhat.com/show_bug.cgi?id=2184640
Despite the fact that some critical
On Sat, Jun 24, 2023 at 6:36 PM Chris Adams wrote:
> Once upon a time, Aleksandra Fedorova said:
> > When you build a package in CentOS Koji it gets into c9s-gate tag [1].
> > These packages are publicly available and if you'd like to use or test
> them
> > before their RHEL part passed the
Once upon a time, Aleksandra Fedorova said:
> When you build a package in CentOS Koji it gets into c9s-gate tag [1].
> These packages are publicly available and if you'd like to use or test them
> before their RHEL part passed the internal RHEL QE, you can do that.
>
>
Hi,
On Sat, Jun 24, 2023 at 6:09 PM Michael Catanzaro
wrote:
>
>
> On Sat, Jun 24 2023 at 10:24:58 AM -0500, Chris Adams
> wrote:
> > Is there any chance of having a CentOS Stream repo along the lines of
> > Fedora's updates-testing, so that CVEs at least would have some type
> > of
> >
On Sat, Jun 24 2023 at 10:24:58 AM -0500, Chris Adams
wrote:
Is there any chance of having a CentOS Stream repo along the lines of
Fedora's updates-testing, so that CVEs at least would have some type
of
available update in a timely manner? With 7 there's the fasttrack
repo,
but it doesn't
On Sat, Jun 24 2023 at 03:26:46 PM +, Gary Buhrmaster
wrote:
If one does find a security update that did not get
streamed, is there a way for a non-customer[0] to
open an appropriate ticket both now, and in the
future when RH moves their internal bug tracker
to jira[1]?
Yes, you do not
On Sat, Jun 24, 2023 at 3:05 PM Michael Catanzaro wrote:
> But in practice, we actually currently have a lot of desynced packages
> where RHEL is ahead of CentOS Stream for various reasons. I believe
> most such cases are mistakes that need to be corrected, not intentional
> delays. E.g. if a
Once upon a time, Michael Catanzaro said:
> So here is the reality with security updates. The vast majority of
> security updates are shipped in RHEL 3-9 months after we fix them,
> because minimizing the quantity of updates is an important goal in
> RHEL to reduce update churn for customers, so
On Sat, Jun 24 2023 at 08:53:32 AM -0500, Chris Adams
wrote:
Is it? At one point, there were considerable gaps in security
updates;
RHEL 9.x would get an update while CentOS Stream 9 (as the target for
RHEL 9.[x+1]) didn't get a corresponding update for quite a while. If
Stream doesn't get
Once upon a time, Neal Gompa said:
> I will also point out that CentOS Stream is perfectly suitable for
> production use
Is it? At one point, there were considerable gaps in security updates;
RHEL 9.x would get an update while CentOS Stream 9 (as the target for
RHEL 9.[x+1]) didn't get a
On Fri, Jun 23, 2023 at 6:09 PM Kevin Kofler via devel
wrote:
>
> Josh Boyer wrote:
> > Agree with Matthew fully here. We've been working rather hard
> > internally to adjust the development process for RHEL to be more
> > collaborative and open than it ever has before.
>
> The *development
Josh Boyer wrote:
> Agree with Matthew fully here. We've been working rather hard
> internally to adjust the development process for RHEL to be more
> collaborative and open than it ever has before.
The *development process* is more open, but the production releases, which
is the only thing end
Matthew,
Thanks for sending this out. There is a lot of FUD right now and this plan
is what I had hoped was going on. The FPO/RH/IBM should do some additional
community engagement to clear this up. A very clear diagram of the
development/packaging flow would go a long way and give the community a
On Thu, Jun 22, 2023, at 11:01 AM, Matthew Miller wrote:
> 1. Fedora Rawhide continually updated
> 2. ELN maintained in parallel, as part of Fedora
> 3. At some point, ELN branched to new CentOS Stream
> 4. ... a year or so of CentOS Stream development in public ...
> 5. RHEL Beta forked from
On 6/22/23 19:01, Matthew Miller wrote:
Sure, but... that's the _opposite_ of the direction things are going.
Awesome post.
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
___
devel mailing list -- devel@lists.fedoraproject.org
To
On Thu, Jun 22, 2023 at 5:02 AM Matthew Miller wrote:
>
> >> ELN is a build of (some) Fedora packages with EL-specific options, so
> >> it requires Fedora.
> > ELN can exist off an internal non fedora tree. Just depends who is
> > updating the tree.
>
> Sure, but... that's the _opposite_ of the
>> ELN is a build of (some) Fedora packages with EL-specific options, so
>> it requires Fedora.
> ELN can exist off an internal non fedora tree. Just depends who is
> updating the tree.
Sure, but... that's the _opposite_ of the direction things are going.
Previously, what happened to make a major
45 matches
Mail list logo
