Release 5.0.2 #1457
Merged
Release 5.0.2 #1457
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Reported with nhibernate#1438
fredericDelaporte
force-pushed
the
5.0.2
branch
2 times, most recently
from
a5cb3dd to
d3894e9
Compare
fredericDelaporte
force-pushed
the
5.0.2
branch
from
d3894e9 to
70500af
Compare
|
I've moved #1455 to bugs, as it is technically a bugfix. Could you please regenerated the release notes? |
hazzik
approved these changes
Nov 28, 2017
|
Adjusted. I intend to do the release tomorrow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I guess we do not have more things to add in 5.0.2, so here is the release PR.
Release draft is view-able for NHibernate team here.
Elaborated from a draft generated with:
(If you test it, it announces 14 commits because it counts on master in spite of the
-c 5.0.xwhich told it the branch. That parameter is still useful for correctly setting the target of the draft release.)The GitReleaseManager settings have been updated for handling new tags.
I have also added a commit for retro-documenting a missing possible breaking change of 5.0.0.