On Sat, Apr 23, 2022 at 7:26 PM Mikolaj Izdebski <mizdebsk(a)redhat.com> wrote:
On Sat, Apr 23, 2022 at 9:32 AM Mattia Verga via devel
<devel(a)lists.fedoraproject.org> wrote:
>
> Il 22/04/22 19:14, Mikolaj Izdebski ha scritto:
> > In one week modello package will be updated in rawhide (Fedora 37)
> > from version 1.11 to version 2.0.0.
> >
> > Bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2053953
> > PR:
https://src.fedoraproject.org/rpms/modello/pull-request/4
> >
> > The new major version introduces API break and packages may need to be
> > ported to work with the new version.
> >
> > Packages that build-require modello and are possibly affected by this update:
> >
> > antlr-maven-plugin
> > maven
> > maven-archetype
> > maven-assembly-plugin
> > maven-doxia
> > maven-doxia-sitetools
> > maven-file-management
> > maven-invoker-plugin
> > maven-plugin-tools
> > maven-remote-resources-plugin
> > maven-scm
> > maven2
> > plexus-sec-dispatcher
> > xmvn
> >
> >
> > --
> > Mikolaj Izdebski
>
> Please build it in a side-tag, so that affected package maintainers can
> try to rebuild their packages there and the final update can be delayed
> until you're sure to not break anything.
Using side tags for single build updates is an overkill. There are
many different ways of testing packages, most of them don't involve
using sidetags. But if anyone actually wants to test modello update in
a sidetag, let me know and I will create one.
I think Mattia wanted to say that this should not be a single-build
update at all, given that it breaks API and probably requires changes
in dependent packages. Hence, the update + all required adaptations
should only be pushed together, as a single update.
Fabio