On 10/23/20 8:01 AM, Dominik 'Rathann' Mierzejewski wrote: > On Friday, 23 October 2020 at 14:45, Aleksandra Fedorova wrote: > [...] >> You can blame me for being not clear enough, if you want, but I'd >> rather move on and use the current GCC11 work as an example which >> shows the real power of the ELN proposal, and the real benefit for >> Fedora which it brings. >> >> Despite the accusation of us bypassing the Fedora Change process, we >> are doing a different thing. >> >> GCC11 will definitely go through the Change process as usual. > That's reassuring. Absolutely. And as I've mentioned before on this thread, we're trying to figure out how to drop that change in earlier than we have in the past. There's technical as well as non-technical concerns. The time period Jakub and myself were looking at was dropping it in at the end of stage1 upstream gcc development which would be mid Nov. But we both feel it's imperative that the implications be discussed here and that the change in procedure gets highlighted in the usual change proposal. >> This activity could have been done internally in RHEL, or externally >> in some upstream working groups. But ELN now allows us to do this work >> in public in Fedora, and invite Fedora community to join it, if they >> _want_. > How can we join, then? How is this better than doing this, say, in COPR? > Or a rawhide side-tag. Right now the build is on a side tag and hasn't been merged into ELN (to the best of my knowledge). Once the bits are merged in then I expect anyone can join in the "fun". > >> As we promised by the ELN Change we have provided the platform for GCC >> upstream, RHEL downstream and Fedora community to collaborate on the >> work for Fedora, and motivation for Red Hat to sponsor this effort. > So far I haven't seen any clear instructions on how I can, say, rebuild > my packages with GCC11 to catch any fall-out early. Or where you're > going to publish (if at all) the results of any rebuilds you'll perform. We don't generally publish them -- though we've certainly discussed it in the past and the only impediment is my time. The jenkins server which drives my testing is on Red Hat's internal network, but there's a publisher that would allow us to push the build info out to a public facing server. There's nothing inherently private and/or secret about the work. We also use that jenkins system to do wide scale testing of GCC work before it lands in upstream GCC. If you have specific packages in mind, I'm happy to let you know their build status with gcc-11. It's just some clicking. jeff _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
