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
Changelog 42.2.24 #2258
Changelog 42.2.24 #2258
Conversation
I just found that some dates of the releases don't correspond with the real release date on Maven Central, I could send a commit fixing those in your branch also a small clean-up of empty sections. |
Just in case: the release becomes official only after the official announcement at pgsql-jdbc mailing list, so it can easily be so that artifacts are deployed a couple of days before the announcement. |
Ok, there is a small mismatch on what we consider the release date, the official announcement (at pgsql-announce mailing list) is normally after the artifacts are deployed, yet the date in the changelog is normally set to the commit date of the changelog, and even that might not be correct since the artifacts could be deployed after. The most prominent example is the 4.2.20 release:
Anyway, this is a discussion for another time. |
Ya, I'm not terribly worried about the mismatch in dates. Thanks for the review though |
I have pushed a commit to your branch (you can do a pull to get the change in your local branch) with some small fixes in the formatting structure, and also removed the last item since it looks like a duplicate for the second item. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't checked the items one by one but LGTM
I'm going to let this age for a day then push it tomorrow, tag it and release it. |
Then this is a reminder to update the date to |
Last version before 42.3.0
Want to leave a working version of 42.2.x