On Fri, Oct 23, 2020 at 10:43 PM Neal Gompa <ngompa13(a)gmail.com> wrote:
..skipped..
There's actually nothing wrong with this idea in itself, because
at
the crux of it is that there is a desire to have a side-tag to build
gcc11 with a limited compose to regression test and further evaluate
the development of GCC earlier. This is something I'd like to have
available for more things, and it's a great idea. But there is
basically no reason to stuff it into ELN other than it already exists
as a gap in our existing process. Instead, I'd like to have that
formally approved by FESCo in a way that releng would make a dedicated
side tag for it and allow OSCI to be configured for mini-composes for
the purpose of assisting in GCC development. Then it can be a regular
part of GCC rebase processes.
On top of generic sidetag functionality, ELN has additional features
like automated continuous rebuilds of Rawhide packages, regular
composes and container builds[1], and people watching after them.
Note that we have spent three months on ELN automation and it still
has a lot of gaps in it.
Collaboration between GCC11 maintainers and ELN SIG allows us to save
the resources, both technical and human, and use the already existing
infrastructure pieces built for ELN to temporarily (for three weeks)
test the GCC11 too.
You are suggesting now that someone goes and duplicates this work. If
you know people somewhere ready to do this, let them step in and we
can discuss it.
I also don't see why you think that landing GCC11 in ELN three weeks
ahead on Rawhide contradicts with the idea of ELN being a development
preview of future RHEL.
[1]
https://docs.fedoraproject.org/en-US/eln/deliverables/
--
Aleksandra Fedorova
bookwar