kopia lustrzana https://gitlab.com/sane-project/website
66 wiersze
2.6 KiB
HTML
66 wiersze
2.6 KiB
HTML
|
<!-- received="Fri Nov 19 22:29:43 1999 PST" -->
|
|||
|
|
<!-- sent="20 Nov 1999 02:29:00 -0400" -->
|
|||
|
|
<!-- name="Kevin Dalley" -->
|
|||
|
|
<!-- email="kevind@rahul.net" -->
|
|||
|
|
<!-- subject="Numbering schemes for snapshots" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="" -->
|
|||
|
|
<title>sane-devel: Numbering schemes for snapshots</title>
|
|||
|
|
<h1>Numbering schemes for snapshots</h1>
|
|||
|
|
<b>Kevin Dalley</b> (<a href="mailto:kevind@rahul.net"><i>kevind@rahul.net</i></a>)<br>
|
|||
|
|
<i>20 Nov 1999 02:29:00 -0400</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#188">[ date ]</a><a href="index.html#188">[ thread ]</a><a href="subject.html#188">[ subject ]</a><a href="author.html#188">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0189.html">Oliver Rauch: "Please test sane cvs - soname of backend libs"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0187.html">John Vickers: "Re: The Sane mailing list is regurgitating old messages"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
I would like the snapshots to be numbered so that it is obvious:<br>
|
|||
|
|
<p>
|
|||
|
|
1. Whether one snapshot is more recent than another snapshot.<br>
|
|||
|
|
<p>
|
|||
|
|
2. Whether a snaphot is more recent than an official release, and<br>
|
|||
|
|
vice versa.<br>
|
|||
|
|
<p>
|
|||
|
|
I prefer that the release numbers are monotonically increasing.<br>
|
|||
|
|
<p>
|
|||
|
|
I package versions of sane for Debian and I want the automatic<br>
|
|||
|
|
updating to work flawlessly, whether I package an official release or<br>
|
|||
|
|
a snapshot. Currently, I am using a version number of<br>
|
|||
|
|
1.0.1-1999-10-21, which uses the CVS tag DEVEL_1_9. Perhaps 1.0.1-1.9<br>
|
|||
|
|
would make more sense as a version number. By including the 1.0.1<br>
|
|||
|
|
version number, I can make sure that 1.0.2, when it gets release, will<br>
|
|||
|
|
be greater than 1.0.1-1999-10-21-5. It is nice to know that 1.0.2 ><br>
|
|||
|
|
1.0.1-1999-10-19-21 > 1.0.1.<br>
|
|||
|
|
<p>
|
|||
|
|
I don't really know how the versions should be numbered, but I like<br>
|
|||
|
|
including the 1.0.1 in the release number.<br>
|
|||
|
|
<p>
|
|||
|
|
Are there any other ideas out there.<br>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
Kevin Dalley
|
|||
|
|
<a href="mailto:kevind@rahul.net">kevind@rahul.net</a>
|
|||
|
|
<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="0189.html">Oliver Rauch: "Please test sane cvs - soname of backend libs"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0187.html">John Vickers: "Re: The Sane mailing list is regurgitating old messages"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|