On Mon, Apr 25, 2022 at 1:38 PM Mattia Verga via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Il 24/04/22 22:06, Mikolaj Izdebski ha scritto: > > On Sun, Apr 24, 2022 at 1:56 AM Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > >> On Sat, Apr 23, 2022 at 7:26 PM Mikolaj Izdebski <mizdebsk@xxxxxxxxxx> wrote: > >>> On Sat, Apr 23, 2022 at 9:32 AM Mattia Verga via devel > >>> <devel@xxxxxxxxxxxxxxxxxxxxxxx> 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. > > I've just built Modello 2.0.0 in Koji: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1955290 > > Anyone interested can test dependent packages against this build. > > If dependent packages need to be fixed to work with updated Modello, > > their builds can be submitted together with Modello as a multi-build update. > > Otherwise I'll submit Modello 2.0.0 as a single-build Bodhi update on Friday. > > > > -- > > Mikolaj Izdebsk > > > > > As said before, you should (must) not submit the update as a single > build update, because this will break dependent packages in rawhide. Do you have any evidence for this claim that the update will break any package? If so, please share it. > You must build your package in a side-tag and coordinate with > maintainers of dependent packages OR take care of rebuild those packages > in the side-tag OR ask any provenpackager to do so (if the primary > maintainer is unresponsive). See > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#updating_inter_dependent_packages 1. There is no evidence that the update is going to break anything. 2. The link refers to "Later Branched and stable releases" section, while I'm preparing update only for rawhide. 3. This section of update guide does not even mention side tags. 4. This is not a policy, but just a guide, an outdated one. Updates policy does not require maintainers to use side tags in this case. -- Mikolaj Izdebski > > Mattia > > > _______________________________________________ > 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 > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
