Add missing databases releases in our changelog

[ipfaze]

Thanks to @brandon-welsch, we found out that there are databases releases that are not mentioned in our changelog.

For example, the PostgreSQL last changelog release was made on 11 August 2022 for version 12.11.0-3 as you can see below:

Since then, multiple PostgreSQL versions were released.

⚠️ PostgreSQL may not be the only database that missed some releases.

An investigation must be done to determine which releases are missing and add them afterwards in our changelog section.

[yohann-bacha]

Concerning the issue with Postgres, it has been fixed since I updated Postgres versions.

I made some investigation, here what I found

Mysql

On admin

8.0.33-1
5.7.38-1

On changelog

C'est ok

Elasticsearch

On admin

7.10.2-2
6.8.23-1

On changelog

It's ok

Influx

On admin

1.8.10-1

On changelog

ok

Mongo

On admin

4.0.27-1
3.6.23-1

On changelog

Last is 4.0.19-1 and 3.6.19-1 in 2020

Postgres

On admin

14.8.0-1
13.11.0-1
12.15.0-1
11.20.0-1

On changelog

Redis

On admin

7.0.10-1
6.2.11-1
5.0.14-1

On changelog

ok

As you can see, the only changelog entry we did not do is for available MongoDB versions. Do we really want to communicate on these version as we are not supporting them anymore? @ipfaze @brandon-welsch

[brandon-welsch]

@yohann-bacha I think we can at least display it in the changelog, by setting a date in the past. The communication on twitter is not needed

[ipfaze]

Thanks for your investigation @yohann-bacha but you checked for latest databases versions where I talked about all versions.

For example, if your search about the PostgreSQL 14.0.0-1 release. It does not appear at all in our changelog.

So, some versions are totally missing in our changelog.
This is the reason of this issue, we need to search and found missing releases and add it afterwards to keep a full release history.

[yohann-bacha]

Okay, but why would we do such a refactoring of versions which are not available to use anymore? (just to know the reason)

[EtienneM]

I don't think this is really important. It would be a really boring job to make the diff between all databases versions available on Scalingo and the changelog entries. Moreover I don't really see the advantages of doing this work. Hence I think we can close this issue. What do you think @ipfaze?

[ipfaze]

We discussed about it during our team retrospective and we still want to tackle it.