Skip to content

Conversation

a-velasco
Copy link
Contributor

@a-velasco a-velasco commented Sep 5, 2025

Issue

Release notes, release information, and legacy/modern charm information is scattered throughout the docs and GitHub. It is unclear where to look for information related to PostgreSQL charm versions.

Solution

  • Created explanation/charm-versions/index - overview of all major PostgreSQL charm versions, including 14 vs. 16, and legacy vs. modern
  • Updated explanation/charm-versions/legacy-charm - clarified difference between PG 16 and 14 in the context of the legacy charm, and removed some information that is irrelevant to 16. Moved some information about modern charms into the modern-charm page.
  • Created explanation/charm-versions/modern-charm - explained the differences between 14 and 16, and some context about the differences between these modern charms compared to the legacy charm.

Checklist

  • I have added or updated any relevant documentation.
  • I have cleaned any remaining cloud resources from my accounts.

@a-velasco a-velasco added the documentation Improvements or additions to documentation label Sep 8, 2025
@a-velasco a-velasco marked this pull request as ready for review September 8, 2025 12:14
@a-velasco a-velasco added the enhancement New feature, UI change, or workload upgrade label Sep 8, 2025
@a-velasco a-velasco changed the title Update versions and release documentation Update versions and release documentation (16) Sep 15, 2025
@taurus-forever
Copy link
Contributor

Thank you @a-velasco !
BTW, why docs publishing has failed for the PR?

@a-velasco a-velasco merged commit 90a2f7e into 16/edge Sep 22, 2025
4 of 5 checks passed
@a-velasco a-velasco deleted the release-docs-16 branch September 22, 2025 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature, UI change, or workload upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants