Replies: 3 comments 5 replies
-
|
Yes, sure. Simply state when you want me to generate a new release: I usually skim through the delta of 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 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.0Oh, 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? |
Beta Was this translation helpful? Give feedback.
-
|
The longer the times between changes/PRs, and releases the more memory of what was done and why fades. 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). |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions