kopia lustrzana https://gitlab.com/sane-project/website
101 wiersze
4.9 KiB
HTML
101 wiersze
4.9 KiB
HTML
<!-- received="Sat Nov 13 06:41:42 1999 PST" -->
|
|
<!-- sent="Sat, 13 Nov 1999 22:44:34 +0800" -->
|
|
<!-- name="Petter Reinholdtsen" -->
|
|
<!-- email="pere@hungry.com" -->
|
|
<!-- subject="Re: next release?" -->
|
|
<!-- id="199911131444.WAA29757@minerva.cc.uit.no" -->
|
|
<!-- inreplyto="next release?" -->
|
|
<title>sane-devel: Re: next release?</title>
|
|
<h1>Re: next release?</h1>
|
|
<b>Petter Reinholdtsen</b> (<a href="mailto:pere@hungry.com"><i>pere@hungry.com</i></a>)<br>
|
|
<i>Sat, 13 Nov 1999 22:44:34 +0800</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#116">[ date ]</a><a href="index.html#116">[ thread ]</a><a href="subject.html#116">[ subject ]</a><a href="author.html#116">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0117.html">Christoph: "Re: Another Microtek Phantom 636 Problem"</a>
|
|
<li> <b>Previous message:</b> <a href="0115.html">Thorsten Pfaff: "Mustek works!!!"</a>
|
|
<li> <b>Maybe in reply to:</b> <a href="0085.html">William L. Sebok: "next release?"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0119.html">Kai Haberzettl: "Re: next release?"</a>
|
|
<li> <b>Next in thread:</b> <a href="0118.html">Oliver Rauch: "Re: next release?"</a>
|
|
<li> <b>Reply:</b> <a href="0119.html">Kai Haberzettl: "Re: next release?"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
[Oliver Rauch]<br>
|
|
<i>> I think we should make more CVS snapshots and put a link from the</i><br>
|
|
<i>> sane homepage to the current stable CVS snapshot.</i><br>
|
|
<p>
|
|
That would be a good idea. My page with into on how to get the CVS<br>
|
|
tree should also be moved to the SANE homepage. If I knew there was<br>
|
|
interest, I could make daily or weekly snapshots available from my web<br>
|
|
page.<br>
|
|
<p>
|
|
<i>> But I am not sure if all backend authors do use sane CVS. It is</i><br>
|
|
<i>> important that every backend is up to date in the CVS or is made up</i><br>
|
|
<i>> to date at least once a month if there have been any important</i><br>
|
|
<i>> changes.</i><br>
|
|
<p>
|
|
Currently you, me, David and Kevin Charter has write access to the CVS<br>
|
|
tree. I believe all backend maintainers should have write access to<br>
|
|
the tree, to keep their backend up to date.<br>
|
|
<p>
|
|
Some days ago, when I found time to look at SANE again, I scanned thru<br>
|
|
the mailing list, and included the latest backend versions I found<br>
|
|
announced there. I probably missed some, but I hope the next snapshot<br>
|
|
will contain most of the updated backends.<br>
|
|
<p>
|
|
This is then a call to all maintainers to let me know if I forgot<br>
|
|
their backend when updating. Check the ChangeLog, and send me an<br>
|
|
email if you want your backend updated.<br>
|
|
<p>
|
|
<i>> We should call out an "keep the CVS code up to date"-phase now and</i><br>
|
|
<i>> some weeks later we should call a "test the CVS version"-phase.</i><br>
|
|
<i>> Some more weeks later we should call a "code freeze - only</i><br>
|
|
<i>> bugfixes"-phase. Then we can use CVS to get a new, STABLE version!</i><br>
|
|
<p>
|
|
Good idea. I'm working on it.<br>
|
|
<p>
|
|
To make sure everyone understands how this works, I'll try to outline<br>
|
|
how and when I will change the CVS tree. The punchline is : I will<br>
|
|
not change backends. All backend updates (except dll and net) must be<br>
|
|
sent to the backend maintainer, which will review the patch and<br>
|
|
possibly take it. If the backend maintainer releases a new backend or<br>
|
|
want me to update the tree, I will update tree. dll and net are<br>
|
|
special as there is no current maintainer. I will review the patch<br>
|
|
and commit it if I like it. :-)<br>
|
|
<p>
|
|
For all the other code, I will update if I am pretty sure the change<br>
|
|
not breaks something else, or if it is a bugfix. All changes to the<br>
|
|
logic or API must be approved by discussions on this list, and I<br>
|
|
expect such changes to be done by David directly.<br>
|
|
<p>
|
|
All patches must include a ChangeLog. No ChangeLog -> no CVS update<br>
|
|
(unless it fixes some of my problems with SANE - as usual :-).<br>
|
|
<p>
|
|
All this should be common sense. :-)<br>
|
|
<pre>
|
|
--
|
|
##> Petter Reinholdtsen <## | <a href="mailto:pere@td.org.uit.no">pere@td.org.uit.no</a>
|
|
<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="0117.html">Christoph: "Re: Another Microtek Phantom 636 Problem"</a>
|
|
<li> <b>Previous message:</b> <a href="0115.html">Thorsten Pfaff: "Mustek works!!!"</a>
|
|
<li> <b>Maybe in reply to:</b> <a href="0085.html">William L. Sebok: "next release?"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0119.html">Kai Haberzettl: "Re: next release?"</a>
|
|
<li> <b>Next in thread:</b> <a href="0118.html">Oliver Rauch: "Re: next release?"</a>
|
|
<li> <b>Reply:</b> <a href="0119.html">Kai Haberzettl: "Re: next release?"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|