On Mon, Jun 19, 2023 13:02:45 +0200, Vít Ondruch wrote:
Dne 19. 06. 23 v 11:55 Ankur Sinha napsal(a):
<snip>
>
> We're discussing a different topic now.
Sorry but we don't. The thread started with: "For the 99% of packages I
maintain I usually perform the same workflow
when updating them". I don't see that percentage could be in line with the
update policy.
It really depends on what these packages are (and had I assumed that was
hyperbole anyway). It sure wouldn't apply to 99% of my (or the
neuro-sig) packages, but would to quite a few.
To re-iterate: everyone should remember to check what impact their
package builds/updates have on other packages before building/pushing
(even for rawhide).
> The thread was "these steps are
> repetitive, how do folks automate them", and we're now discussing
> "maintainers should remember to check the impact of update before
> pushing them".
Being maintainer of ~200 packages, I certainly don't suffer the
repetitiveness, because there is rarely need to update the stable releases,
following the update policy.
Again, it really depends on your packages. You maintain lots of core
libraries where API/ABI bumps etc. do not/should not be pushed to stable
releases. For the neuro-sig, we do have quite a few python packages that
have frequent minor/patch releases and we do push these as updates to
stable branches also after doing impact checks. So, I do use my script
for these.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London