elasticsearch versions numbering algorithm - elasticsearch

In the versions history of the Elasticsearch one can see a 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 would appreciate if anybody can explain (or give a link to appropriate document) why such versioning is being applied.
What is the reason to develop 1.3.x when 1.4.x versions are already available?
When 1.4.x are being developed, 1.3.x further development will consist only in bug fixes, or new features are being added also?

Assuming Elasticsearch uses Semantic Versioning, they are backporting patches for maintenance reasons (e.g. security vulnerability). This bumps the PATCH version (the "x" in 1.3.x).
No new features would be added to 1.3.x. Whenever a new feature is added, the MAJOR or MINOR version is bumped (e.g. 1.3.x → 1.4.x).
Disclaimer: I'm not an Elasticsearch maintainer so I can't say with certainty what versioning system they use.

Related

How do I update my VS 2017 to the latest version of SSDT?

I'm using VS 2017. I'm starting a project which involves SQL Server Analysis Services and I wanted to make sure I had the latest SSDT installed in VS. I first upgraded VS to 15.9.5. I looked and noticed that SSDT was still at 15.1.61901, instead of 15.8.2 (the latest version). I then downloaded and installed the latest SSDT and the version is still at 15.1.61901 (see below). Am I missing a step here?
Go to "Add/Remove Programms" and check the Version-Number:
You'll see the "build number" here. To translate it to the "release number" go to SSDT download page and check the version informations:
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
Version Information:
Release number: 15.9.0
Build Number: 14.0.16186.0
Release date: January 28, 2019

How to install WebSphere 7.0 Trial

I have successfully installed WAS ND 8.5.5 trial version but have been asked to certify an app against WAS 7.
Because there is now WAS 9, I think the direct link to the 7 repo has been removed from the public site for Devs: https://developer.ibm.com/wasdev/downloads/#asset/WAS_traditional_for_Developers
Anyone know how I can add the repo for WAS 7 to the installation manager so I can certify my app against it?
The End of Market date for WAS 7 was Dec 16th 2016, and it is going out of service on Apr 30th 2018.
So you can no longer obtain new copies of WAS 7 (nor would you want to, I hope).

Which version of SonarQube contains the fix for SLVS-1122

I am getting permissions related errors in my analysis because the process is requesting write access. Before the analysis task starts, if I uncheck the read-only box for the source folder the error does not happen. That is why I'm looking for this fix -
https://jira.sonarsource.com/browse/SLVS-1122
According to the commends on that link, SonarAnalyzer for .Net 1.21 wasn't released until at least Jan 30th. Will this fix be in SonarQube 5.6.6, or will I have to wait until 5.7?
edit: currently running version 5.6.4 through TFS 2015 onprem
You're mixing apples and oranges. The fix you want is in the most recently released version of SonarC#. You can upgrade it in your SonarQube server (mostly) independently of your SonarQube server version.

SonarQube 5.5 and Views plugin

As per SQ 5.5 release notes, it seems “Views” plugin would be deprecated and replaced by “Governance” plugin.
Please refer to following ticket for more details : https://jira.sonarsource.com/browse/SONAR-7428
What would be the support option for anyone using "views" plugin
with community edition?
SQ 5.5 release date was 22 April 2016 but it has not been released as of 25 April 2016. What is the new release date for SQ 5.5 release?
SonarQube 5.5 will be officially released at the end of April / early beginning of May.

Is there a planned release date for sonarqube 5.2?

Apparently, SonarQube 5.2 won't need a connection string to push build data. (I discovered this by having a look at the sonar.runner vso-build-tasks earlier this morning).
When will this version be available?
SonarQube 5.2 is expected late October 2015 / early November 2015.
Update: SonarQube 5.2 was released on November 2th, 2015.

Resources