Skip to content

Remove docs (16)#1851

Open
a-velasco wants to merge 3 commits into
16/edgefrom
deprecate-docs-16
Open

Remove docs (16)#1851
a-velasco wants to merge 3 commits into
16/edgefrom
deprecate-docs-16

Conversation

@a-velasco

@a-velasco a-velasco commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Documentation for PostgreSQL 16 has moved to the 16/docs branch of the postgresql-single-kernel-library repository.

This PR removes all Sphinx Stack (Starter Pack) documentation and tooling.

All URLs to the docs being removed are automatically redirected to the newest domain.

Checklist

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

@a-velasco a-velasco requested a review from a team as a code owner July 13, 2026 11:43
@a-velasco a-velasco requested review from carlcsaposs-canonical, dragomirp, juju-charm-bot, marceloneppel and taurus-forever and removed request for a team July 13, 2026 11:43
@a-velasco a-velasco changed the title Deprecate docs 16 Remove docs (16) Jul 13, 2026
@a-velasco a-velasco added documentation Improvements or additions to documentation not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes labels Jul 13, 2026
@github-actions github-actions Bot added the Libraries: Out of sync The charm libs used are out-of-sync label Jul 13, 2026

@carlcsaposs-canonical carlcsaposs-canonical left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the git history of the 16/docs branch of postgresql-single-kernel-library as expected? it looks like it contains code & workflows

also we might want to enable rulesets for branch protection on the docs branches

@a-velasco

Copy link
Copy Markdown
Contributor Author

is the git history of the 16/docs branch of postgresql-single-kernel-library as expected? it looks like it contains code & workflows

also we might want to enable rulesets for branch protection on the docs branches

Yes, all of this is expected/known. The 16/docs branch in single-kernel is getting cleaned up, and I need push permissions to both /docs branches for the moment.

@taurus-forever taurus-forever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should leave breadcrumbs to the new documentation location for people who want to contribute...

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 Libraries: Out of sync The charm libs used are out-of-sync not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants