kopia lustrzana https://gitlab.com/sane-project/website
95 wiersze
4.7 KiB
HTML
95 wiersze
4.7 KiB
HTML
|
<!-- received="Sun Jul 18 10:47:20 1999 PDT" -->
|
|||
|
|
<!-- sent="Sun, 18 Jul 1999 19:42:12 +0200" -->
|
|||
|
|
<!-- name="Andreas" -->
|
|||
|
|
<!-- email="andreas.rick@free.fr" -->
|
|||
|
|
<!-- subject="Re: Release early, release often" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="Release early, release often" -->
|
|||
|
|
<title>sane-devel: Re: Release early, release often</title>
|
|||
|
|
<h1>Re: Release early, release often</h1>
|
|||
|
|
<b>Andreas</b> (<a href="mailto:andreas.rick@free.fr"><i>andreas.rick@free.fr</i></a>)<br>
|
|||
|
|
<i>Sun, 18 Jul 1999 19:42:12 +0200</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#104">[ date ]</a><a href="index.html#104">[ thread ]</a><a href="subject.html#104">[ subject ]</a><a href="author.html#104">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0105.html">georgewu@mediaone.net: "Microtek X6EL problem"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0103.html">Peter Kirchgessner: "Update hp-backend"</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="0107.html">Nick Lamb: "Re: Release early, release often"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
Petter Reinholdtsen wrote:<br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> I'm one of the strange programmers who beleave in the slogan "Release</i><br>
|
|||
|
|
<i>> early, release often". I find the release rate of SANE too late and</i><br>
|
|||
|
|
<i>> too slow.</i><br>
|
|||
|
|
<p>
|
|||
|
|
I agree to that.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> To get the "current" version of SANE, I have to fetch the latest</i><br>
|
|||
|
|
<i>> release and patches from all over the world to get the latest backends</i><br>
|
|||
|
|
<i>> and frontends. I beleave this is a problem easily solved using</i><br>
|
|||
|
|
<i>> version control software and by giving more then one person write</i><br>
|
|||
|
|
<i>> access to the master source. With a public read-only source tree, us</i><br>
|
|||
|
|
<i>> wanting to do development on SANE don't have to wait 3-6 months to see</i><br>
|
|||
|
|
<i>> if our patches made into the distribution.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> To solve this problem I sat up a CVS tree at cvs.hungry.com with</i><br>
|
|||
|
|
<i>> public read-only access from anoncvs.hungry.com, and gave the current</i><br>
|
|||
|
|
<i>> maintainer David write access to the server. Before the backend</i><br>
|
|||
|
|
<i>> maintainers get write access, David have to say OK.</i><br>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<i>> The CVS tree is hardly used at all. I beleave the reason for this is</i><br>
|
|||
|
|
<i>> that David is unfamiliar with CVS, and also want to keep the master</i><br>
|
|||
|
|
<i>> source under his control, and not on some random source code</i><br>
|
|||
|
|
<i>> repository set up by a complete stranger. I hope I'm mistaken.</i><br>
|
|||
|
|
<p>
|
|||
|
|
I'm not too familiar with CVS myself, but I'm willing to learn.<br>
|
|||
|
|
<br>
|
|||
|
|
<i>> If this situation don't change, I've been thinking about using the CVS</i><br>
|
|||
|
|
<i>> server for SANE development myself, collecting all reasonable patches</i><br>
|
|||
|
|
<i>> and commiting them into my own branch, releasing snapshots every week</i><br>
|
|||
|
|
<i>> (or more often), like Alan Cox is releasing his experimental version</i><br>
|
|||
|
|
<i>> of Linux. I do not want to do this, as it will generate a code fork,</i><br>
|
|||
|
|
<i>> and unless most or all SANE developers colaborates, the CVS version</i><br>
|
|||
|
|
<i>> would be only for my benifit.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Am I wasting my time?</i><br>
|
|||
|
|
<p>
|
|||
|
|
No! I think you may save some by this initiative...<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Among the things I would like to fix with SANE are Win32 support,</i><br>
|
|||
|
|
<i>> better network support (access control and encrypted communication)</i><br>
|
|||
|
|
<i>> and improving SnapScan and Coolscan backends. Until the development</i><br>
|
|||
|
|
<i>> model changes, it seems a waste to start working on these.</i><br>
|
|||
|
|
<p>
|
|||
|
|
I wouldn't mind injecting my work on the Coolscan Backend into CVS.<br>
|
|||
|
|
It needs some changes to sane.h and I was wondering what I have<br>
|
|||
|
|
to do to get them accepted and included.<br>
|
|||
|
|
<p>
|
|||
|
|
Andreas<br>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<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="0105.html">georgewu@mediaone.net: "Microtek X6EL problem"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0103.html">Peter Kirchgessner: "Update hp-backend"</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="0107.html">Nick Lamb: "Re: Release early, release often"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|