Talk:Bugday Wishlist

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 10:41, 5 November 2024 (UTC)
:: Your reply ~~~~

Bad topic - Version bumps

Talk status

This discussion is done.

Interesting to see the example of a bad topic, a version bump. I actually thought I was helping doing that. I have a PR open, that indeed got no attention, since 26th of May. The underlying bug #696414 has been open since October 2019. This new version is available since June 2016 upstream. The question remains how do we keep packages to current, if core gentoo developers have no time do it, and don't want people to help them? Hfern (talk) 06:12, 8 June 2020 (UTC)

I think the point here is that it's no use to "rush" multiple "copy-paste" -style contributions on a bugday. Sometimes, and more often, these "rotting" ebuilds require a lot more to look into, than just copypasting an ebuild file. Then it's on the devs doing review to check all updates, fixes, testing etc, and it takes away from real purpose of bugday. We are checking and merging contributions to maintainer-needed packages all the time, and we'd wish whoever made those contributions, really cared about the package and checked upstream before version bumping.

Proxied_Maintainer_FAQ#.22Copy.2Fpaste.22_style_of_contributions

Juippis (talk) 12:40, 10 June 2020 (UTC)

Seems like this is answered with a good example however reopen if you feel like more clarification is needed.

Immolo (talk) 22:19, 12 March 2023 (UTC)