Automatic update for wxGTK3-184.108.40.206-1.fc33.
* Sun May 10 2020 Scott Talbert <firstname.lastname@example.org> - 220.127.116.11-1
- Update to new upstream release 18.104.22.168
sudo dnf upgrade --advisory=FEDORA-2020-35061137b7
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by bodhi
Why was there no 3.0.5 update for F32?
Because nobody asked for it? Do you have a need for it?
Well, nothing severe like known to fix bug X in Y. But I considered a F32 bugfix update as consistent with stable update policy, as F32 is a fresh release: "As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. The update rate for any given release should drop off over time, approaching zero near release end-of-life; since updates are primarily bugfixes, fewer and fewer should be needed over time."
Yes, I believe it would be okay to update it per policy. However, I usually wait until there is some compelling reason (e.g., a bug that someone is affected by) before pushing an update to a package that I maintain.
In this case, I think updating to 3.0.5 in stable will also need to be coordinated with the dependent packages to ensure there are no breakages due to the change in wxDataView:
I have seen at least one application that has crashes on 3.0.5 and not 3.0.4 because of this change.
OK, understandable to stay on 3.0.4.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.