Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prepare changes for new release 1.5.1 #405

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

Melkij
Copy link
Collaborator

@Melkij Melkij commented Jun 9, 2024

I think we have consensus to release a new version.

I had some free time to compile a list of changes. New version number was already commited earlier. Also I noticed another place in META.json where the minimum version of postgresql needed to be updated.

Mostly list of changes, new version number was already commited earlier. Also I noticed another place (in META.json) where the minimum version of postgresql needed to be updated.
@andreasscherbaum
Copy link
Collaborator

Looks good.

Couple related questions:

  • Can you document your release process in the Wiki?
  • Does this release deserve an announcement on .org?
  • Is this automatically uploaded to PGXN? Or is this a manual process?

@Melkij
Copy link
Collaborator Author

Melkij commented Jun 10, 2024

The release steps are documented in doc/release.rst

But I've never actually did a full release myself. In the past, I would prepare changes for release in git and then @dvarrazzo would review and complete the rest of the steps. (not sure if I have access to PGXN)

@Melkij Melkij merged commit 3edf5b3 into reorg:master Jun 12, 2024
10 checks passed
@MasahikoSawada MasahikoSawada mentioned this pull request Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants