On Tue, 2007-08-07 at 05:40 -0400, Michael Cummings wrote: > > sure...except in another thread, we're saying it's ok for non-maintainers to > bump packages, and i'm here to tell you, when that happens they rarely confirm > things like missing deps or whether it dies during a build.
What? They won't confirm if it is missing deps or dies during a build. Sounds like they should not be doing a bump and or committing anything :) Testing is a must before committing anything to the main tree, regardless of it being unstable, masked, etc. > most often, when a > non-maintainer bumps a package its because they need the newer version and > feel > competent enough to do the bump themselves (regardless of whether they know > what > they're looking at). the || die would bite us in those cases Surely if they aren't testing their own bump. Then they really have no business messing with another's package, or any for that matter if they fail to test. > - don't know about > you all, but i get more than annoyed at bugs on package bumps for bumps > that weren't coordinated with the maintainer. It's likely best for maintainers to be contacted before a bump or etc. Not sure I would require it, depends on if one will be responsible for their own actions or not. If not, then it's not right to bump without maintainers knowledge and leave them to deal with any problems. -- William L. Thomson Jr. Gentoo/Java
signature.asc
Description: This is a digitally signed message part
