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

Bump repmgr version 5.5.0 #868

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Bump repmgr version 5.5.0 #868

wants to merge 1 commit into from

Conversation

gonzalemario
Copy link
Contributor

No description provided.

@gonzalemario gonzalemario requested a review from a team November 6, 2024 15:51
README.md Outdated Show resolved Hide resolved
#define REPMGR_VERSION_NUM 50400
#define REPMGR_EXTENSION_VERSION "5.4"
#define REPMGR_EXTENSION_NUM 50400
#define REPMGR_RELEASE_DATE "2022-XX-XX"
Copy link
Collaborator

Choose a reason for hiding this comment

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

I believe the XX are needed. Check the Makefiles

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If I understand, that variable affects only what we put in https://www.repmgr.org/docs/5.3/install-requirements.html, in the "current" release.

I haven't found it in any other place, maybe we just added the "XX-XX" because we didn't know in advance when a new released would be publised?

If we keep the Xs, we would see this

$ awk '/^#define REPMGR_RELEASE_DATE / { print $3; }' repmgr_version.h.in | cut -d '"' -f 2
2024-XX-XX

I'll generate the docs to discard.

@martinmarques
Copy link
Collaborator

It's missing a repmgr--5.4-5.5.sql file for the upgrade of the extension

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.

2 participants