Changelog

[rahilsondhi]

Adds a new Changelog to the Docs

[github-actions]

Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-rahil-changelog

[billy-the-fish]

Timescale follows the Google developer style guide. A few comments to align your cool words with the guide.

[billy-the-fish]

I really like that we are adding information about all products, great.

For consistency, can we stick to products rather than dates in the titles:

Timescale Cloud

May 31, 2024

[rahilsondhi]

But many posts will have content that span multiple products 🤔 That's why I went with a date approach, because this post was a grab bag of stuff (two new extensions and one PopSQL improvement)

[rahilsondhi]

Check out the titles on this page. That's the style I was going for. The idea is that it catches the user's attention, like "ohh I'm interested in the git integration, and I can see git is in the title"

[billy-the-fish]

Hmmm nice point, and I like their doc.

All Hex releases are all done by date. To be consistent in this page, you need to change the TimescaleDB 2.15.2 header to "June 7th 2024 update" . I'd keep to specific date, patch releases can come out pretty fast.

@pallavisontakke, @fabriziomello are you ok with this?

[shahriarpshuvo]

Added a PR on web-documentation repo:
https://github.com/timescale/web-documentation/pull/712
This need to merge first to see the reflection.

[billy-the-fish]

Thanks for the changes, they look great. Nearly there.

[billy-the-fish]

Hmmm nice point, and I like their doc.

All Hex releases are all done by date. To be consistent in this page, you need to change the TimescaleDB 2.15.2 header to "June 7th 2024 update" . I'd keep to specific date, patch releases can come out pretty fast.

@pallavisontakke, @fabriziomello are you ok with this?

[rahilsondhi]

See #3249