ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Versioning policies for .NET and CPP
Date Fri, 18 Dec 2015 09:03:46 GMT
Is this change only offered for .NET releases or for Java as well?

On Fri, Dec 18, 2015 at 12:42 AM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Folks,
>
> We have some versioning policies in Java. Normaly Java version looks like
> "A.B.C.[suffix]", where [suffix] could potnetially be anything - "b", "p",
> "rc", "ga", "final", etc.
>
> In .NET/CPP on Windows we have to follow standard versioning format
> "A.B.C.D", where D is a value between 0 and 65536. The quesion is how to
> map string suffix to some numerical value.
>
> I have an idea to rely on release date. E.g.
> 1) Take year of the last major release as a starting point.
> 2) Amount of hours spent from starting point is a value of D. Hours, not
> years because several releases could potnetially happen in the same day.
>
> E.g.:
> - Last major release was in 2015
> - Today is 12/18/2015
> - D = 24 * 340 /* days since 01/01/2015 */ + 6 /* hours */ = Ignite.NET
> 1.5.0.8166.
>
> *Pros:*
> - Newer versions always have bigger "D" component. GA will be greater than
> beta, patch 2 will be greater than patch 1, etc..
> *Cons:*
> - Version have to be updated just before release.
>
> Does anyone have concerns/thoughts about it?
>
> Vladimir.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message