Hello,

As illustrated by Nathan question on GitHub 
<https://github.com/nhibernate/nhibernate-core/issues/1396>, I think we 
need to know how we plan developments since the 5.0.0 release.

In my view, after such a release with many changes, we now are in a period 
where we are somewhat awaiting regression reports, and fix them. That 
should be the 5.0.1 release. Some minor changes like documentation fixes 
are also done within it.

The only remaining regression is currently a perf loss 
<https://github.com/nhibernate/nhibernate-core/issues/1391>, having a PR 
<https://github.com/nhibernate/nhibernate-core/pull/1394> which Alexander 
wishes to review.
I think that after that we should release 5.0.1.

Maybe could we include some additional "old" bug fixes too, like this 
<https://github.com/nhibernate/nhibernate-core/pull/1389> or this 
<https://github.com/nhibernate/nhibernate-core/pull/1406> if their PR are 
finalized soon, but I do not think we should linger long on that patch 
release.

After that, I think we should start merging things for 5.1 (which add 
features or fixes bugs but do not introduce breaking changes). In case of 
additional lately reported regressions mandating a 5.0.2, we would add a 
5.0.x branch for fixing them.

What is you own point of view?

Best regards,

Frédéric Delaporte

Side note: about 5.0.0, there are also some dependent projects which seem 
to lack active contributors while some user have expressed they are waiting 
for a 5.0 version. Mainly Validator 
<https://github.com/nhibernate/NHibernate-Validator> and Spatial 
<https://github.com/nhibernate/NHibernate.Spatial>. If anyone a bit 
knowledgeable about those could upgrade them to NHibernate 5.0, that would 
be great.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nhibernate-development+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to