Please stabilize =dev-cpp/aixlog-1.4.0 Thanks
First of all, it's a custom to wait at least 30 days with ~KEYWORDS to catch any user reported errors / tinderbox. Then why you need this stabilized? It hasn't been stabilized prior at all, does a stable package need it?
(In reply to Joonas Niilola from comment #1) > First of all, it's a custom to wait at least 30 days with ~KEYWORDS to catch > any user reported errors / tinderbox. I know for 30 days practice, it's been in tree for few days less than that so I think any potential issues would be reported by now and besides, this is a small package. > Then why you need this stabilized? It hasn't been stabilized prior at all, > does a stable package need it? No, a stable package does not need it, but if it works fine I don't see why not to go with stabilization. Unless the arch teams are overwhelmed with other work, in that case I apologise and feel free to close my other stablereq bugs :-)
(same comments apply for other bugs you commented on, I don't want to copy-paste)
(In reply to Jakov Smolić from comment #2) > > I know for 30 days practice, it's been in tree for few days less than that > so I think any potential issues would be reported by now and besides, this > is a small package. It was added 20 days ago. Github may show the date wrongly if you've opened PR 30 days ago, but it was *added* 20 days ago. Just check the git log on your sync repository, or https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=95b9a8b2f8d2c58fda8943debae1ab4cc64f3c0e (commit date) > No, a stable package does not need it, but if it works fine I don't see why > not to go with stabilization. Unless the arch teams are overwhelmed with > other work, in that case I apologise and feel free to close my other > stablereq bugs :-) Last time I checked we had +60 stabilization bugs open for proxy-maint project and it started feeling like we're being ignored. We're probably last on their list anyway, but it's looking much better now with "only" ~25 stabilization bugs open. In general if there are no *users* asking for a stabilization, or any stable package doesn't depend on it, let's avoid useless work. Of course if you yourself use a stable system and need this package there, or at work environment etc, then you're a user who needs it. But don't stabilize for the sake of stabilizing. It'll be annoying to maintain the package in the long run. But please wait the 30 days before you continue. https://wiki.gentoo.org/wiki/Project:AMD64_Arch_Testers#Arch_tester.27s_policy (it says "check that the ebuild is at least 30 days old and without modifications" but you had a stabilization bug open for a package where you just did PYTHON_COMPAT update... PYTHON_COMPAT python-3.9 is stable-masked so you can continue there)
(In reply to Joonas Niilola from comment #4) > (In reply to Jakov Smolić from comment #2) > > > > I know for 30 days practice, it's been in tree for few days less than that > > so I think any potential issues would be reported by now and besides, this > > is a small package. > > It was added 20 days ago. Github may show the date wrongly if you've opened > PR 30 days ago, but it was *added* 20 days ago. Just check the git log on > your sync repository, or > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=95b9a8b2f8d2c58fda8943debae1ab4cc64f3c0e > (commit date) I know and track when was all of my packages' versions are added. It's not like I asked for stabilization after a week :) Plus I had few other packages that were stablilized after ~2 weeks and nobody ever objected. Unless I have to wait 30 days just for the sake of the number 30 I don't see anything wrong with asking for stabilization few days earlier if it's a small packages and has no known bugs. > > No, a stable package does not need it, but if it works fine I don't see why > > not to go with stabilization. Unless the arch teams are overwhelmed with > > other work, in that case I apologise and feel free to close my other > > stablereq bugs :-) > > Last time I checked we had +60 stabilization bugs open for proxy-maint > project and it started feeling like we're being ignored. We're probably last > on their list anyway, but it's looking much better now with "only" ~25 > stabilization bugs open. > > In general if there are no *users* asking for a stabilization, or any stable > package doesn't depend on it, let's avoid useless work. Of course if you > yourself use a stable system and need this package there, or at work > environment etc, then you're a user who needs it. But don't stabilize for > the sake of stabilizing. It'll be annoying to maintain the package in the > long run. Ok, thank you for the advice.
