-
Notifications
You must be signed in to change notification settings - Fork 128
Prepare for release 2.2 #1069
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 for release 2.2 #1069
Conversation
|
Feel free to delay this for additional PRs and tests. I'll update the changelog as needed. |
f741267 to
f257d90
Compare
|
Thanks for preparing the release. Please have a look at #1019 and more importantly how to test for upgrades. Then test for upgrades using packages, if you have time to do that. If I remember correctly the idea was to use patch updates (2.1.1, 2.1.2, etc) when the monitor schema does not change, and minor updates (2.1 to 2.2, etc) for “bigger” updates with monitor schema change. The recent versions we published warranted a version number change of the “minor update” fashion, but did not change the monitor schema. We still need empty schema upgrade files. |
f257d90 to
e3319c9
Compare
* Add CHANGELOG entry for the release * Update version number throughout * Update version related tests
e3319c9 to
b5f23db
Compare
I'll see what I can do. |
See the README at https://github.com/hapostgres/pg_auto_failover/tree/main/tests/upgrade where I documented the process I used to follow before releasing new versions. |
|
Sadly I wasn't able to build the docker image with the
This way I'm not able to test an upgrade in the way you linked. |
|
Good afternoon, @dimitri |
|
Thanks for contribution @hashworks ; I now have published the new release! |
|
Fantastic @dimitri ! Thanks a bunch ❤️ |
Loosely followed the previous #1017.