nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-11 05:33:47 +01:00
Code Issues Packages Projects Releases Wiki Activity

Clarify chosen tag progression

Browse Source 
svn:r3047
This commit is contained in:
Nick Mathewson 2004-11-30 16:07:20 +00:00
parent 3929f58018
commit a889926e1c
1 changed files with 7 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
src/or/or.h
View File

@ -1644,17 +1644,14 @@ void clear_trusted_dir_servers(void);
* encounter two versions that differ only by status tag, we compare them
* lexically.
*
* Now, we start each development branch with (say) 0.1.1.1-cvs. The
* patchlevel increments consistently as the status tag changes, for example,
* as in: 0.1.1.2-alpha, 0.1.1.3-cvs, 0.1.1.4-alpha, 0.1.1.5-cvs, 0.1.1.6-rc
* 0.1.1.7-cvs, 0.1.1.8-rc, 0.1.1.9-cvs. Eventually, we release 0.1.1.10.
* The stable CVS repository gets the version 0.1.1.11-maint_cvs; the
* next patch release is 0.1.1.12.
* Now, we start each development branch with (say) 0.1.1.1-alpha.
* The patchlevel increments consistently as the status tag changes,
* for example, as in: 0.1.1.2-alpha, 0.1.1.3-alpha, 0.1.1.4-rc
* 0.1.1.5-rc, Eventually, we release 0.1.1.6. The next patch release
* is 0.1.1.7.
*
* XXXX(Alternatively, we could go: 0.1.1.1-alpha, 0.1.1.1-alpha_cvs,
* 0.1.1.2-alpha, 0.1.1.2-alpha_cvs . This wouldn't violate our
* only-one-release-per-number rule, since CVS versions aren't
* released. Roger?)
* Between these releases, CVS is versioned with a -cvs tag: after
* 0.1.1.1-alpha comes 0.1.1.1-alpha-cvs, and so on.
*/
typedef struct tor_version_t {
int major;