elasticsearch versions numbering algorithm -


in versions history of elasticsearch 1 can see nontrivial suquence of versions, e.g.

elasticsearch 1.4.2 december 16, 2014 elasticsearch 1.3.7 december 16, 2014 elasticsearch 1.4.1 november 26, 2014 elasticsearch 1.3.6 november 26, 2014 elasticsearch 1.4.0 november 05, 2014 elasticsearch 1.3.5 november 05, 2014 elasticsearch 1.4.0.beta1 october 01, 2014 elasticsearch 1.3.4 september 30, 2014 

i appreciate if can explain (or give link appropriate document) why such versioning being applied.

what reason develop 1.3.x when 1.4.x versions available?

when 1.4.x being developed, 1.3.x further development consist in bug fixes, or new features being added also?

assuming elasticsearch uses semantic versioning, backporting patches maintenance reasons (e.g. security vulnerability). bumps patch version (the "x" in 1.3.x).

no new features added 1.3.x. whenever new feature added, major or minor version bumped (e.g. 1.3.x → 1.4.x).

disclaimer: i'm not elasticsearch maintainer can't certainty versioning system use.


Comments

Popular posts from this blog

powershell Start-Process exit code -1073741502 when used with Credential from a windows service environment -

twig - Using Twigbridge in a Laravel 5.1 Package -

c# - LINQ join Entities from HashSet's, Join vs Dictionary vs HashSet performance -