In tree for 130 days. Is it ready? Remember to file stabilisation requests for your packages. If it's ready, add CC-ARCHES to the 'keywords' field of this bug.
HINT: Flameshot 11.0 released: + CLI-mode + new functions [ https://github.com/flameshot-org/flameshot ] Perhaps it might be more beneficial to directly stabilize this enhanced version? Thanks. Bug 831475 - media-gfx/flameshot-10.0.0:0 version bump [ https://bugs.gentoo.org/show_bug.cgi?id=831475 ]
(In reply to Sam James from comment #0) > In tree for 130 days. Is it ready? Remember to file stabilisation requests > for your packages. If it's ready, add CC-ARCHES to the 'keywords' field of > this bug. Am I qualified to stabilize self-maintained (by me) packages? I have almost no experience in "thoroughly testing" packages, could you please provide me with detailed instructions how to do that?
(In reply to Pavel Kalugin from comment #2) > (In reply to Sam James from comment #0) > > In tree for 130 days. Is it ready? Remember to file stabilisation requests > > for your packages. If it's ready, add CC-ARCHES to the 'keywords' field of > > this bug. > > Am I qualified to stabilize self-maintained (by me) packages? I have almost > no experience in "thoroughly testing" packages, could you please provide me > with detailed instructions how to do that? https://devmanual.gentoo.org/keywording/index.html#moving-from-arch-to-arch Given it already has a stable version, primary thing to look out for is if you know of any regressions compared to the stable 0.6.0 (even if not perfect, is the chosen new version a worse user experience than 0.6.0?). At the base mostly just need feedback from someone using+following the package that can say "yes, it's ready" with some confidence (preferably by filling stabilization bugs themselves, but otherwise just setting CC-ARCHES if someone else did). That aside, it may make sense to update the summary+package list to 0.10.2 at this point, been in the tree for over 30 days and by semver x.x.2 is are intended for bugfixes rather than introduce breaking changes (not to say it's always the case). Typically a better stable candidate.
To clarify, no need to look /too/ deep into it -- especially for a standalone package (this isn't going to break other packages).
Is it possible to stabilize 0.10.2 instead? It's been in the tree for more than 30 days, I've been using this version for a long time and had no issues with it.
Sounds good. Pavel, if you agree to stabilizing 0.10.2, please add CC-ARCHES to Keywords field.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a773ad363c246ef5d67581f7006b15a353459f99 commit a773ad363c246ef5d67581f7006b15a353459f99 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2022-03-17 08:56:34 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2022-03-17 08:56:54 +0000 media-gfx/flameshot: stabilize 0.10.2 for x86 Closes: https://bugs.gentoo.org/828361 Signed-off-by: Joonas Niilola <juippis@gentoo.org> media-gfx/flameshot/flameshot-0.10.2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=04628d662b75cb81fcb5e349a668e3fead348b40 commit 04628d662b75cb81fcb5e349a668e3fead348b40 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2022-03-17 08:54:05 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2022-03-17 08:56:54 +0000 media-gfx/flameshot: stabilize 0.10.2 for amd64 Bug: https://bugs.gentoo.org/828361 Signed-off-by: Joonas Niilola <juippis@gentoo.org> media-gfx/flameshot/flameshot-0.10.2.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
