Bumping (almost) all YaST packages to version 4.4.x (15.4.x)
Version Bump ------------ https://yastgithubio.readthedocs.io/en/latest/versioning/#new-schema-version... TLDR: For next Leap 15.4/SLE 15-SP4 we need to bump all package versions to 4.4.x. Unfortunately we forgot to do that in 15.3/SP3 so not all YaST packages have version 4.3.x there. :-( So to avoid this situation again we did the version bump right now. **All YaST packages have been updated to 4.4.0 unless they already use a 4.4.x version.** Exceptions ---------- The skelcd-control-* and system-role-* packages use the product version so I updated them to version 15.4.0. Skipped Packages ---------------- skelcd-control-suse-manager-proxy, skelcd-control-suse-manager-server - these packages use the SUSE Manager version yast-rake - this is a Ruby gem, not an YaST module, it uses usual semantic versioning patterns-yast-20201210 - it uses date as the version These packages do not use 4.x version so I kept them untouched, they are maintained by other teams and I do not know their versioning schema: yast-hana-firewall-2.0.4 yast-hana-update-1.2.1 yast-rmt-1.3.2 yast-samba-provision-1.0.4 yast-sap-ha-1.0.9 yast2-aduc-2.2 yast2-gpmc-1.5.1 If you do not have any particular reason for that versioning it would be nice if you unified the package versions to 4.4.x. Then next time the version bump would happen globally with the other YaST packages. If you have any questions, just ping me. -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8
On Tue, 20 Apr 2021 19:10:03 +0200 Ladislav Slezak <lslezak@suse.cz> wrote:
Version Bump ------------
https://yastgithubio.readthedocs.io/en/latest/versioning/#new-schema-version...
TLDR: For next Leap 15.4/SLE 15-SP4 we need to bump all package versions to 4.4.x.
Unfortunately we forgot to do that in 15.3/SP3 so not all YaST packages have version 4.3.x there. :-( So to avoid this situation again we did the version bump right now.
**All YaST packages have been updated to 4.4.0 unless they already use a 4.4.x version.**
Exceptions ----------
The skelcd-control-* and system-role-* packages use the product version so I updated them to version 15.4.0.
Just be carefull with skelcd-openSUSE which use date version, but(!) for Leap 15.4 it should use new version. I am not sure if we already have new branch for it. Josef
Skipped Packages ----------------
skelcd-control-suse-manager-proxy, skelcd-control-suse-manager-server - these packages use the SUSE Manager version
yast-rake - this is a Ruby gem, not an YaST module, it uses usual semantic versioning
patterns-yast-20201210 - it uses date as the version
These packages do not use 4.x version so I kept them untouched, they are maintained by other teams and I do not know their versioning schema:
yast-hana-firewall-2.0.4 yast-hana-update-1.2.1 yast-rmt-1.3.2 yast-samba-provision-1.0.4 yast-sap-ha-1.0.9 yast2-aduc-2.2 yast2-gpmc-1.5.1
If you do not have any particular reason for that versioning it would be nice if you unified the package versions to 4.4.x. Then next time the version bump would happen globally with the other YaST packages.
If you have any questions, just ping me.
Dne 20. 04. 21 v 19:21 josef Reidinger napsal(a):
Just be carefull with skelcd-openSUSE which use date version, but(!) for Leap 15.4 it should use new version. I am not sure if we already have new branch for it.
Good point! I have created the openSUSE-15_4 branch from openSUSE-15_3 and set the version to 15.4.0. If you do any fix to 15.3 do not forget to merge it also to 15.4! -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8
On 4/20/21 6:10 PM, Ladislav Slezak wrote:
Version Bump ------------
https://yastgithubio.readthedocs.io/en/latest/versioning/#new-schema-version...
TLDR: For next Leap 15.4/SLE 15-SP4 we need to bump all package versions to 4.4.x.
Unfortunately we forgot to do that in 15.3/SP3 so not all YaST packages have version 4.3.x there. :-( So to avoid this situation again we did the version bump right now.
**All YaST packages have been updated to 4.4.0 unless they already use a 4.4.x version.**
Thanks Ladislav! I would modify this paragraph in the documentation: "The major and minor numbers are properly bumped before the product release in case no divergence has been introduced during the development phase." I would indicate that the version should be bumped right after branching in order to adapt it to the new product number. Regards, Iván -- José Iván López González YaST Team at SUSE LINUX GmbH IRC: jilopez
participants (3)
-
josef Reidinger -
José Iván López González -
Ladislav Slezak