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

5.1.0 release #1525

Merged
merged 8 commits into from
Mar 17, 2018
Merged

5.1.0 release #1525

merged 8 commits into from
Mar 17, 2018

Conversation

fredericDelaporte
Copy link
Member

@fredericDelaporte fredericDelaporte commented Jan 11, 2018

In order to avoid forgetting breaking changes, here is a start of release notes.

Copy link
Member Author

@fredericDelaporte fredericDelaporte left a comment

Choose a reason for hiding this comment

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

I have already updated the release notes and prepared the GitHub release draft.

* In GitHub, make sure no open issues have milestone set to the release
that is about to happen (as these will show in the release notes).
Copy link
Member Author

Choose a reason for hiding this comment

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

as these will show in the release notes

No more true with GitReleaseManager. It only takers into account closed PR/issues.


* Create a draft release in Github with GitReleaseManager. If you have used
the NHibernate build menu, it should be available in Tools\gitreleasemanage.x.x.x\
(change x.x.x by its current version in tools).
Copy link
Member Author

Choose a reason for hiding this comment

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

Its chocolatey version is obsolete and unable to work with current GitHub.

@fredericDelaporte fredericDelaporte changed the title [WIP] Preparing 5.1.0 release [WIP] 5.1.0 release Mar 11, 2018
releasenotes.txt Outdated
* #1403 Add timeouts support to MultiCriteria
* #1377 Logging refactoring
* #954 NH-3807 - Support for .NET Core 2.0
* #948 NH-3435 - Ability to select the root entity in a criteria projection
Copy link
Member

Choose a reason for hiding this comment

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

I think this issue needs to be renamed to "Ability to select entities in a criteria projection" . As implementation #1471 is not limited to root entity.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.


** Highlights
* NHibernate has gained two new target frameworks: .Net Core 2.0 and .Net Standard 2.0. NHibernate NuGet package
provides them, along with the .Net framework 4.6.1 build.
Copy link
Member

@hazzik hazzik Mar 11, 2018

Choose a reason for hiding this comment

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

Need to mention limitations:

  • Binary serialization is not supported - the user shall implement serialization surrogates for System.Type, FieldInfo, PropertyInfo, MethodInfo, ConstructorInfo, Delegate, etc.
  • other limitations mentioned in the PR.

If no error or other issue requiring further changes occurred, merge
the release PR and wait for the resulting commit CI release build.

* Retrieves the artifacts of the CI release build.
Copy link
Member

Choose a reason for hiding this comment

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

Retrieve

hazzik
hazzik previously approved these changes Mar 12, 2018
@fredericDelaporte fredericDelaporte changed the title [WIP] 5.1.0 release 5.1.0 release Mar 15, 2018
@fredericDelaporte
Copy link
Member Author

fredericDelaporte commented Mar 16, 2018

So well, what about #626 "Split database providers into own projects"? I have reviewed it one more time and approved it only two minor adjustments are to be done in my opinion (now done). And I still think it would be valuable to have it in 5.1.

This aside, what should be the "immediate" plan:

  • Release this in its current state (or NH-4008 - Split database providers into own projects. #626 included but nothing else)?
  • And right after that:
    • Observe a 5.0 similar "cooldown" period, just merging regressions, simple bugs or minor improvements, till releasing a 5.1.1?
    • Merge things for a 5.2?
    • Go straight to merging things for a 6.0, especially removing the accumulated obsoletes and handling 6.0 TODOs?

@hazzik
Copy link
Member

hazzik commented Mar 16, 2018

  1. Release this in its current state
  2. Observe a 5.0 similar "cooldown" period, just merging regressions, simple bugs or minor improvements, till releasing a 5.1.1
  3. Merge things for a 5.2 and call it 6.0 if enough new features are emerged

@ngbrown
Copy link
Contributor

ngbrown commented Mar 16, 2018

Observe a 5.0 similar "cooldown" period, just merging regressions, simple bugs or minor improvements, till releasing a 5.1.1

Regressions and bugs ideally would be on a 5.1.x branch so 5.2 changes can immediately be merged to trunk.

@fredericDelaporte fredericDelaporte merged commit 2f703d0 into nhibernate:master Mar 17, 2018
@fredericDelaporte fredericDelaporte deleted the 5.1.0 branch March 17, 2018 08:22
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.

4 participants