Why doesn't Curator follow the same versioning as ELK?

[DarrienG (Darrien Glasser)]

It is clearly updated regularly, the last update happened like 20-odd days ago.

If curator isn't dead, why isn't the version numbering the same as all of the other ELK products?

This makes zero sense and is very confusing when every other compatibility matrix looks like this:

The latest version of Curator should be version 6.5 and even if there are no changes, it should be updated with the version numbers of everything else.

If it just so happens to be compatible with more than the other products, that's fine. It's confusing that everything else follows a rigid compatibility matrix, but curator does not.

[theuntergeek (Aaron Mildenstein)]

Curator does not follow the general versioning because:

• It's not a product, like Logstash, Beats, Kibana, etc.
• Curator has different cross-version compatibility from everything else
• It's developed and maintained by one person
• It is being supplanted (at least, in large part) by Index Lifecycle Management, which is slated to arrive in Elasticsearch 6.6.0.

Because of the drive to build in Curator-like functionality, which is part of a product, Curator will continue to exist, but as a side project, and will likely continue to be developed and supported by one person.

[DarrienG (Darrien Glasser)]

It would be really nice if this were specified in the Curator repo for instance. It's under the official elastic/ repo on GitHub.

It also sort of follows the same versioning conventions as the other products which makes it extra confusing.

ELK has been great though, so thanks for contributing