Thanks. I'll reference this in a discord-bin commit I'm about to push which explains the rationale we can apply to this too (although signal doesn't break on new versions immediately). Fine if maintainer just stabilises when they wish too.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=20d6dce99ba2f294c829ec9ee3fadc3370c49917 commit 20d6dce99ba2f294c829ec9ee3fadc3370c49917 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-12-21 02:17:02 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-12-21 02:19:15 +0000 net-im/discord-bin: stabilize 0.0.16-r4 for amd64 Common package which users want and it'd be nice if they didn't have to learn about p.accept_keywords quite-so-immediately after trying out Gentoo. Ideally should stable a few days after adding new versions although given that IIRC each new version breaks old ones immediately, straight-to-stable should be fine for future bumps if that's the case. It's not like it makes any practical difference at all to users, as currently the stable folks just use the ~arch latest anyway. i.e. this is just a convenience thing. (Tagging signal-desktop-bin as it's the same idea there, although it doesn't break on bumps, the rest of the logic applies. Maintainer may just wish to stable after a few days.) Bug: https://bugs.gentoo.org/829731 Signed-off-by: Sam James <sam@gentoo.org> net-im/discord-bin/discord-bin-0.0.16-r4.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
amd64 stable. Closing.
