Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2004:
[Freeciv-Dev] (PR#4712) Version numbering proposal
Home

[Freeciv-Dev] (PR#4712) Version numbering proposal

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: jdorje@xxxxxxxxxxxxxxxxxxxxx
Cc: jdwheeler42@xxxxxxxxx
Subject: [Freeciv-Dev] (PR#4712) Version numbering proposal
From: "Marko Lindqvist" <marko.lindqvist@xxxxxxxxxxx>
Date: Sat, 14 Aug 2004 11:33:19 -0700
Reply-to: rt@xxxxxxxxxxx

<URL: http://rt.freeciv.org/Ticket/Display.html?id=4712 >


  I believe that following scenario would be at least reasonably easy to 
implement and would work quite fine.

  For stable releases, versionstring is of form "AA.BB.CC". For 
development version form is "AA.BB.CC-DDDD (dd.mm.yy hh:mm:ss)".
  AA, BB and CC are in just one file (as in my earlier proof-of-concept 
patch). Same file also decides if current version is stable release or 
development version (IS_DEVEL_VERSION). Changes to this file are updated 
and committed to cvs manually.
  DDDD is number of commits and (dd.mm.yy hh:mm:ss) is last commit time. 
Whole "DDDD (dd.mm.yy hh:mm:ss)" part is automatically generated by cvs 
whenever something gets committed. It lives in separate file. For 
freeciv source it's only a string, so changes to its format have to be 
made at cvs scripts on freeciv.org. I don't know if we would want to 
manually zero commit number after stable release.

  With date and time version string gets awfully long. We can either 
drop  date+time altogether or make automatically updated version file to 
contain two separate strings ("DDDD" and "dd.mm.yy hh:mm:ss") so we can 
use two different strings in C code, one without and second with time 
information.


  -Caz




[Prev in Thread] Current Thread [Next in Thread]