Please mark vendetta-online-bin-1.8.82.ebuild stable.
amd64 stable
Archtested on x86: No issues
(In reply to comment #2) > Archtested on x86: No issues It runs fine, but I hesitate to mark it stable...the first action is to download 1.8.83 update, which is not nice from a arch work point of view. I hereby refuse to stabilise it. amd64 maybe wants to reconsider.
Done.
(In reply to comment #4) > Done. Originally I stayed on this bug to be ready for further discussion, but such an action annoys me. Stabilising moving targets that auto-update on first start-up is a no-go in my eyes.
"I hereby refuse to stabilise it" That's your choice but since you aren't the maintainer it's not really your call if it's marked stable or not. When I file a STABLEREQ bug, I'm not looking for personal opinions from the arch team members. If the package doesn't work on your arch, or if there's some other issue that causes the package to not work, then I would love feedback, but otherwise, kindly get out of the way. The arch team concept already slows things down too much as it is without extra snags.
(In reply to comment #6) > "I hereby refuse to stabilise it" > > That's your choice but since you aren't the maintainer it's not really your > call if it's marked stable or not. When I file a STABLEREQ bug, I'm not > looking for personal opinions from the arch team members. And as far as I understood the concept of architectures, it is not the maintainer's call to just do so. > If the package doesn't work on your arch, or if there's some other issue that > causes the package to not work, then I would love feedback, but otherwise, > kindly get out of the way. The arch team concept already slows things down too > much as it is without extra snags. For multi-package teams where seldomly the whole herd has been tested by the members, the arch team concept finds quite a lot QA and build issues. So either come up with a better concept or kindly get out of the way to let us do our work.
