Release planning for 3.2.12

[nephros]

Hey @Olf0 can we make a release containing #468/#476, as well as the icon problems on 4.6/5.0 (see #472 (comment), #479, and #479 (comment)) in the forseeable future?

The icon thing is harmless but looks bad, this bug affects at least one high-profile patch, and the delta of 3.2.11..master would contain the things already summed up in your draft of 3.2.12 which is a nice set.
There's now also a milestone of that name.

[Olf0]

Yes, sure. Simply state when you want me to generate a new release: I usually skim through the delta of <latest-release-tag>..master for "notable" changes to be recorded in the release changelog before creating a new release.

I can also create an explicitly marked (as part of the RPM file name) beta release, which might be distributed stepwise to a broader audience: First on SailfishOS:Chum:Testing while notifying people at FSO in the corresponding threads (Patchmanager thread, and e.g. specific error report), then (depending on the feedback) by ultimately pushing it to SailfishOS:Chum proper.

It is up to you to assess if some of the changes are "dangerous" (whatever that may mean in this context) enough for being a bit more careful (IIRC you once indicated that).

---

WRT the icon problems on 4.6/5.0

Oh, I wrongly assumed that compiling with the SFOS-SDK for 4.6.0 resolved that!?!

Sure, whatever it needs. Is Vlad available for reviewing changes outside of shell-code, packaging, documentation, CI/CD config, really trivial C(++) code changes?

[nephros]

Oh, I wrongly assumed that #485 resolved that!?!

patchmanager-3.2.11-1.3.1.bso.aarch64, which is the currently available version on Chum for 5.0, still does not show show icons, because 3.2.11 does not include the fix from #464.

[nephros]

The longer the times between changes/PRs, and releases the more memory of what was done and why fades.
Thus the ability to fix any bugs discovered in the wild.

Therefore I'd like you to tag (whenever your get around to it) and release current master (14677a3) as it stands.

After it's released I hope we can finally get #473 in quickly because it extensive but harmless changes make working on feature branches hard (because likelyhood of merge conflicts increases).

[Olf0]

Therefore I'd like you to tag (whenever your get around to it) and release current master (14677a3) as it stands.

Ack. I am planning to mark it as a beta, IIRC I once implemented the provisions (CI config, git-tag format, SFOS-OBS) to easily do that (Checked: that was wishful thinking, hence I tagged it right away); if not, then not (i.e. no beta marking).

But not this weekend, and I cannot assess if I will be able to spare the time during next week, but hope to take care about this next weekend, latest. I'll see how far I can get now.

[Olf0]

Patchmanager 3.2.12 is available at SailfishOS:Chum:Testing. Do you want to notify people at FSO and test yourself first, before I push it to SailfishOS:Chum proper?

BTW, GitHub's CI machinery has significant hickups right now, emitting seemingly arbitrary (and definitely wrong) error messages in 3 tries to run the "CI on tags" workflow.

[nephros]

Great, thank you!

I'll test a bit, and shall alert ruditimmermanns and ichthy to function as beta testers.

[nephros]

Got positive test results myself, at least one confirmation on FSO that the release is working fine.

[Olf0]

O.K., so then https://build.sailfishos.org/request/show/3764

Hence I am also closing this, if issues arise, we can still reopen it.