Exactly.
> I'm not convinced that it's a good idea to give all maintainers the
> ability to create whole releases though. Perhaps having a couple of
> people with that authority would be sufficient to avoid the
> bottleneck problem?
That everyone can does not mean that everyone should. Everyone can
already wrap up their current source and call it a SANE release. That
does not make it a SANE release. General consensus that the given
snapshot is a released and write access to the ftp site is required
for me to accept it as a release.
Social control functions well to regulate this.
> Is there a way to give maintainers restricted write access, say to
> just the part of the package they are responsible for?
It is smarter and easier to let social control take care of this too.
If there is disagreement on some change, it can always be reversed
using CVS.
When a summary of all changes to the current source in addition are
mailed to all maintainers, it is easy to keep track of the changes.
-- ##> Petter Reinholdtsen <## | pere@td.org.uit.no O- <SCRIPT Language="Javascript">window.close()</SCRIPT> http://www.hungry.com/~pere/ | Go Mozilla, go! Go!
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com