On Tue, Oct 13, 2026 at 05:39:42PM +0100, Aoife Moloney via devel-announce wrote: > * Proposal owners: > ** Test critical package set build pipeline in a throw-away side-tag, > address any blocker issues
Hmm, that sounds like you want to push commits to dist-git to do the tests. Why not use copr for this? > ** Switch a couple of packages (eg. popt and rpm itself) to v6 > manually, address any blocker issues > ** Switch v6 on in rpm configuration > ** Watch out for build/test/infra failures caused by the change > ** Address any encountered RPM issues with high priority > ** Assist with dealing with possible fallout in other projects > ** Before mass-rebuild, switch back to v4 if too many issues remain > and postpone to F47 > > * Other developers: > ** Test that any RPM related software they use or maintain continues to > function > ** Report discovered issues for awareness > ** Address incompatibilities in their software > > * Release engineering: > [https://forge.fedoraproject.org/releng/tickets/issues/13546 #13546] > * Policies and guidelines: N/A(not needed for this Change) > * Trademark approval: N/A (not needed for this Change) > * Alignment with the Fedora Strategy: This is a leading development in > the Linux distro space. > > == Upgrade/compatibility impact == > In general, there's little user visible impact, v4 and v6 packages can > peacefully coexist where needed. This is important for 3rd party packages. Some external packages might use the old version for a while. Zbyszek -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
