sane-project-website/old-archive/1999-07/0125.html

77 wiersze
3.8 KiB
HTML

<!-- received="Tue Jul 20 07:40:31 1999 PDT" -->
<!-- sent="Tue, 20 Jul 1999 16:51:43 +0200" -->
<!-- name="Petter Reinholdtsen" -->
<!-- email="pere@hungry.com" -->
<!-- subject="Re: Release early, release often" -->
<!-- id="199907201451.QAA27427@lee.cc.uit.no" -->
<!-- inreplyto="Release early, release often" -->
<title>sane-devel: Re: Release early, release often</title>
<h1>Re: Release early, release often</h1>
<b>Petter Reinholdtsen</b> (<a href="mailto:pere@hungry.com"><i>pere@hungry.com</i></a>)<br>
<i>Tue, 20 Jul 1999 16:51:43 +0200</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#125">[ date ]</a><a href="index.html#125">[ thread ]</a><a href="subject.html#125">[ subject ]</a><a href="author.html#125">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0126.html">Brian Macy: "Re: Release early, release often"</a>
<li> <b>Previous message:</b> <a href="0124.html">Mike Harris: "Re: Microtek ScanMaker IV on Linux-2.2.10 (Redhat 6.0)"</a>
<li> <b>Maybe in reply to:</b> <a href="0101.html">Petter Reinholdtsen: "Release early, release often"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0126.html">Brian Macy: "Re: Release early, release often"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
[Kevin Charter ]<br>
<i>&gt; Given that the individual backends are independent and change a lot</i><br>
<i>&gt; faster (or should, anyway) than the SANE core, this makes sense to</i><br>
<i>&gt; me. It would take a lot of the load off David if he didn't have to</i><br>
<i>&gt; assemble patches for various backends (or other sub-projects)</i><br>
<i>&gt; himself.</i><br>
<p>
Exactly.<br>
<p>
<i>&gt; I'm not convinced that it's a good idea to give all maintainers the</i><br>
<i>&gt; ability to create whole releases though. Perhaps having a couple of</i><br>
<i>&gt; people with that authority would be sufficient to avoid the</i><br>
<i>&gt; bottleneck problem?</i><br>
<p>
That everyone can does not mean that everyone should. Everyone can<br>
already wrap up their current source and call it a SANE release. That<br>
does not make it a SANE release. General consensus that the given<br>
snapshot is a released and write access to the ftp site is required<br>
for me to accept it as a release.<br>
<p>
Social control functions well to regulate this.<br>
<p>
<i>&gt; Is there a way to give maintainers restricted write access, say to</i><br>
<i>&gt; just the part of the package they are responsible for?</i><br>
<p>
It is smarter and easier to let social control take care of this too.<br>
If there is disagreement on some change, it can always be reversed<br>
using CVS.<br>
<p>
When a summary of all changes to the current source in addition are<br>
mailed to all maintainers, it is easy to keep track of the changes.<br>
<pre>
--
##&gt; Petter Reinholdtsen &lt;## | <a href="mailto:pere@td.org.uit.no">pere@td.org.uit.no</a>
O- &lt;SCRIPT Language="Javascript"&gt;window.close()&lt;/SCRIPT&gt;
<a href="http://www.hungry.com/~pere/">http://www.hungry.com/~pere/</a> | Go Mozilla, go! Go!
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0126.html">Brian Macy: "Re: Release early, release often"</a>
<li> <b>Previous message:</b> <a href="0124.html">Mike Harris: "Re: Microtek ScanMaker IV on Linux-2.2.10 (Redhat 6.0)"</a>
<li> <b>Maybe in reply to:</b> <a href="0101.html">Petter Reinholdtsen: "Release early, release often"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0126.html">Brian Macy: "Re: Release early, release often"</a>
<!-- reply="end" -->
</ul>