Skip to content

Release 5.2.6 #2200

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

Merged
merged 1 commit into from
Sep 8, 2019
Merged

Conversation

fredericDelaporte
Copy link
Member

Preparing the release. It currently accounts for pending PRs, async update and dependent transaction fix. If some of them are discarded or delayed to another release, this PR will have to be updated accordingly.

As written by @bahusoid here, some care should be taken when merging to master after the release:

When merging to master this change should be ignored. The following code is expected in master (no need to wrap in new List):

queryInfo.ResultToCache = queryCacheBuilder.Result;

@fredericDelaporte
Copy link
Member Author

Rebased, I will likely release it next Sunday.

@fredericDelaporte fredericDelaporte merged commit f7b64c5 into nhibernate:5.2.x Sep 8, 2019
@fredericDelaporte fredericDelaporte deleted the Release5.2.6 branch September 8, 2019 11:57
@fredericDelaporte
Copy link
Member Author

#2111, in this release, has updated the documentation. But I do not intend to update it on nhibernate.info yet, because it is about a new feature, while we only publish minor version of the documentation, not release version. So updating the 5.2 documentation could be confusing for those attempting to use the feature with a 5.2.5 or below version of NHibernate. I think it should wait 5.3.

@oskarb
Copy link
Member

oskarb commented Sep 8, 2019

#2111, in this release, has updated the documentation. But I do not intend to update it on nhibernate.info yet, because it is about a new feature, while we only publish minor version of the documentation, not release version. So updating the 5.2 documentation could be confusing for those attempting to use the feature with a 5.2.5 or below version of NHibernate. I think it should wait 5.3.

I agree - especially given that it was most likely for a really narrow use case anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants