View Single Post
Posts: 237 | Thanked: 193 times | Joined on Feb 2010 @ Brighton, UK
#6
Originally Posted by Jaffa View Post
I never vote for my own package: it being in Testing is an explicit indication that I think it's worth further testing. I don't believe developers should vote for their own packages (except down ;-)), as it effectively reduces the hurdle from "10 [other] people think the package is suitable" to just nine.

But this isn't an argument I've ever won, so I let it go. There are more important battles to be won.
I'm a relative newbie here so I may have it wrong, but I thought extras-testing was a mandatory step on the way to extras full. So even the mythical perfect application will be put in there at some stage of it's life-cycle. So in many instances it should be holding release candidates and not just betas. Pre-alphas and alphas I would expect to find in extras-devel.

I feel if it' weren't good enough for a release candidate shouldn't the maintainer be pushing to testing with an explicit down-vote to prevent promotion to extras in that case?

Don't worry I'm not looking to reopen any old disagreements, just want to make sure I'm understanding the structure here.

cheers