Re: [vassalengine-devel] stable and unstable releases
Brought to you by:
rodneykinney,
uckelman
From: Joel U. <uck...@no...> - 2007-12-10 18:49:22
|
Thus spake "Rodney Kinney": > > > 1. We need to settle on a policy for the two release series. > > > I see three kinds: > > 1. Stable - default download on the web site > 2. Release Candidate - Available on the web site but labeled as a beta > release > 3. Unstable - could be a nightly build. Available how? Availability of a nightly build is easy---it's something I've setup on SF before. > For version numbering, it's important that old code be able to parse the > version number. Otherwise anybody running a version that's out there right > now wouldn't be able to give a warning when it encounters a more recent > version number. Just to be clear: The requirement is that version v0 of VASSAL be able to correctly order any two versions v1, v2 where at most one of v1 and v2 are after v0, yes? Or do we need it to be the case that, say, VASSAL 2.8.3, can tell which of 3.4.9-rc10 and 7.6.4.2-svn7650 is earlier? -- J. |