Rocky makes sense to me as the next step after Centos8 --Eric
On Tue, Feb 1, 2022 at 1:20 PM ocket 8888 <ocket8...@gmail.com> wrote: > > Hey, that sounds great to me. As far as I'm concerned, this is all the > discussion necessary to move forward. I'm just saying I can't demand > that our project support any particular OS on my own without talking > about it with the list. > > To be clear, I was definitely never going to suggest Alma - not the > least because I couldn't remember the name - or anything else. Rocky > seems like the right choice. And by "going to 7 does sound like moving > backwards" I didn't mean to drop support for CentOS 7, just that > testing on only CentOS 7 instead of updating our CentOS 8 images to > Rocky seemed like the wrong call. I don't think we need to drop > support for that even after being comfortable with Rocky, until it > hits EoL and/or becomes an inconvenience to support. > > On Tue, Feb 1, 2022 at 10:33 AM Dave Neuman <neu...@apache.org> wrote: > > > > +1 to retaining support for 7 until we are good with Rocky. Now *that* is > > something that we can decide as a community. > > > > On Tue, Feb 1, 2022 at 10:31 AM Rawlin Peters <raw...@apache.org> wrote: > > > > > We should probably retain support for CentOS 7 until such a time that > > > we're comfortable with Rocky going forward. I do think Rocky is the > > > future (at least for Comcast that seems to be the case). It's really > > > Rocky vs Alma, and if someone wants to add support for Alma in > > > addition to Rocky and can maintain that support, they should be free > > > to do so. > > > > > > - Rawlin > > > > > > On Tue, Feb 1, 2022 at 10:21 AM ocket 8888 <ocket8...@gmail.com> wrote: > > > > > > > > Yeah, going to 7 does sound like moving backwards - we don't want to > > > > do that, we want to move to whatever is going to be supported now that > > > > CentOS 8 no longer works. The issue is that we need to know that Rocky > > > > Linux is what the ATC project will support if we're going to use it > > > > moving forward, and the working group does not have the authority to > > > > make that call. > > > > > > > > On Tue, Feb 1, 2022 at 9:39 AM Dave Neuman <neu...@apache.org> wrote: > > > > > > > > > > - Need mailing list confirmation that moving to Rocky is the plan, > > > > > then our CI can be converted to Rocky Linux > > > > > > > > > > Do we though? Can't we just put in support for Rocky and if folks > > > > > want > > > > > support for other things they could add it? > > > > > Seems like going to 7 is going backwards for what reason? > > > > > > > > > > On Tue, Feb 1, 2022 at 9:35 AM ocket 8888 <ocket8...@gmail.com> wrote: > > > > > > > > > > > 1. Attendance > > > > > > - Stephen Hamrick > > > > > > - Zach Hoffman > > > > > > - Eric Holguin > > > > > > - Matt Jackson > > > > > > - Srijeet Chatterjee > > > > > > - Taylor Frey > > > > > > 2. CentOS 8 Docker image no longer works > > > > > > - Should we make a workaround or switch to e.g. Rocky Linux ? > > > > > > - Probably depends on overall project direction, but that > > > conversation > > > > > > takes longer than fixing our CI > > > > > > - Issue #6343 needs to be fixed before we could downgrade to only > > > > > > testing on CentOS 7 > > > > > > - Need mailing list confirmation that moving to Rocky is the plan, > > > > > > then our CI can be converted to Rocky Linux > > > > > > 3. ML: ATCv6.1.0-RC2 needs votes > > > > > > - Currently has 2 PMC +1s > > > > > > 4. ML: Summer of Code 2022 > > > > > > > > > > > > On Tue, Feb 1, 2022 at 9:21 AM Zach Hoffman <zrhoff...@apache.org> > > > wrote: > > > > > > > > > > > > > > Consider discussing: > > > > > > > - CentOS 8 no longer works, which breaks our CI. Time to move to > > > Rocky > > > > > > Linux? > > > > > > > > > > > > > > Active mailing list threads: > > > > > > > - Release Apache Traffic Control 6.1.0-RC2 > > > > > > > <https://lists.apache.org/thread/soqqndn7ggzrzjx5s81t7c09yzovll6h> > > > > > > > > > > > > > > On Tue, Jan 25, 2022 at 9:44 AM ocket 8888 <ocket8...@gmail.com> > > > wrote: > > > > > > > > > > > > > > > > If you have anything you want to discuss at next week's meeting, > > > > > > > > respond to this email and it's on the agenda. > > > > > > > > >
