I'd like to drop from portage very outdated net-proxy/3proxy-0.5.3k (which also have issues with repoman) and thus I need to stabilize newer version first. BTW, I'm newbie proxy-maint, so can you give me a hint - am I should try to stabilize every new version, or it's better to avoid adding too much work for arch teams and make stable requests only when some important changes (like security fixes or major feature added) happens? Also, in which cases I should request runtime testing? Of course, I did that testing on my own system (amd64), but how can I know is it required on other arches? In saved searches I see stable requests have "Keywords: STABLEREQ", but https://wiki.gentoo.org/wiki/Stable_request doesn't mention I should set it manually - please let me know if I should do this.
amd64 stable
x86 stable
ppc stable. Closing.
Hi Alex, sorry for missing these questions before. (In reply to Alex Efros from comment #0) > BTW, I'm newbie proxy-maint, so can you give me a hint - am I should try to > stabilize every new version, or it's better to avoid adding too much work > for arch teams and make stable requests only when some important changes > (like security fixes or major feature added) happens? There's no written rules about this, but it is nice to try and find a balance between overloading arch teams and having the stable version being ancient. If upstream regularly makes x.y.z releases I often try to target the last patch release when y is bumped - but this of course depends a lot on how upstream behaves. Ultimately it's up to your discretion as a maintain. > Also, in which cases I should request runtime testing? Of course, I did that > testing on my own system (amd64), but how can I know is it required on other > arches? Again this is subjective, but I am of the opinion that leaf applications like 3proxy are at low risk for arch-specific runtime breakage so there's no point asking arch teams to test that part too. > In saved searches I see stable requests have "Keywords: STABLEREQ", but > https://wiki.gentoo.org/wiki/Stable_request doesn't mention I should set it > manually - please let me know if I should do this. The stabilisation process is in a bit of a state of flux lately. Arch team members that are using newer tools do not require this keyword, but some people are still using older tooling and saved searches that do require it.