Alright, thanks for the explanation.

In that case, I think the RFC is a step in the right direction,
but I don't see it being useful, unless the change owners do the extra
step and file the FTBFS bugs to notify the maintainers.
They can do it already, but don't. Making them finish the change
sooner IMO won't make them to also create the tickets.

In general, I'd like to see any change owner to be responsible for
dependent package breakages to at least the degree of notifying the
maintainer by filling the FTBFS ticket.
Huge sets of wildly interconnected packages are one of the cores of
any distribution, and thoughtfulness is necessary.

--

Michal Schorm
Software Engineer
Databases Team
Red Hat

--

On Mon, Jan 27, 2025 at 8:18 PM Fabio Valentini <decatho...@gmail.com> wrote:
>
> On Mon, Jan 27, 2025 at 8:02 PM Michal Schorm <msch...@redhat.com> wrote:
> >
> > Does this RFC include an obligation for the 'major toolchain upgrades'
> > Fedora Change owners to rebuild the dependent packages ?
>
> No, but this is already happening to some degree.
> For example, test builds with GCC snapshots were actually happening,
> but the results were not communicated to package maintainers before
> the mass rebuild had started - and then it was too late. Making sure
> that the toolchain is in Rawhide one week *before* the mass rebuild
> starts would give a bigger window for that to happen.
>
> Fabio
> --
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue

-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to