Redistimeseries

This is the second milestone release for RedisTimeSeries 1.4.

Headlines:

This release improves overall stability and provides fixes for issues found after the previous milestone release.

Details:
* Bug fixes:
* 454 Disable backfilling for [`TS.INCRBY/DECRBY`](https://oss.redislabs.com/redistimeseries/commands/#tsincrbytsdecrby) commands
* 462 Fix backfilling when `retention > latestTimeStamp`

This is the first milestone release for RedisTimeSeries 1.4.

Highlights:
**Ability to backfill time series!** You can now add samples to a time series where the time of the sample is older than the newest sample in the series. This enables:
- [Adding](https://oss.redislabs.com/redistimeseries/commands/#tsadd) out of order of samples to time series.
- Batch loading of historical samples into an existing series.
- Updating existing samples (for example for compliance reasons).

This has been the most requested feature for RedisTimeSeries. We look forward to your feedback so we can move to a general availability release soon.

Details:
- Added functionality:
- 254 `TS.REVRANGE` and `TS.MREVRANGE` [commands] allow for querying in descending order of Timestamps.(https://oss.redislabs.com/redistimeseries/1.4/commands/#tsmrangetsmrevrange)
- 437 Allow backfilling of samples and updating of existing samples
- Works with [compressed](https://redislabs.com/blog/redistimeseries-version-1-2-is-here/) and uncompressed series.
- This comes with a performance hit when a sample is written out-of-order. We will publish numbers once we are generally available, but are still considering optimisations.
- Missing features to be feature complete
- `TS.DEL` command to delete a sample in the series.
- `NOOO` flag on `TS.CREATE` ("no out of order", we are open to better suggestions :-)) to get the current (v.1.2) behaviour where the series doesn't accept samples out of order.

Notes:
This is not the GA version of 1.4. The version inside Redis will be 10401 or 1.4.1 in semantic versioning. Since the version of a module in Redis is numeric, we could not add an M01 flag.
The docs currently state 1.4 is the latest, this a known bug in our documentation. The latest GA version is still 1.2.

Update urgency: Medium
This is a maintenance release for version 1.2.

Details:

* Bugfixes:
* 414 Crash when a query had an empty label `(foo,)`

Update urgency: Medium
This is a maintenance release for version 1.2.

Details:
* Minor enhancements:
* 403 Support for multi-value filtering in `TS.MGET` and `TS.MRANGE`.

* Bugfixes:
* 378 Using `snprintf` to ensure the same precision of floating-point value replies.
* 374 `TS.RANGE` crashed when COUNT argument was missing.
* 395 Check minimum compatible Redis version at module load time.

Update urgency: Major
This is a major maintenance release for version 1.2.

Details:

* Major Bugfix:
* 358 Potential data corruption due to wrong bit-shifting on insertion of data. This was detected due to [Wrong behaviour](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/redistimeseries/wH0R69e8lOs) in `TS.RANGE`.
* Minor Bugfix
* 353 Crash where the name of a time-series was already taken due to [auto-compaction](https://oss.redislabs.com/redistimeseries/configuration/#compaction_policy-policy).

Update urgency: Medium
This is a maintenance release for version 1.2.

Details:
* Bugfixes:
* 338 reverting 319. Aggregation should happen on deterministic time buckets.

* Known issues:
* 358 Data corruption issue, please skip this version and upgrade to 1.2.5 where this is fixed.