[hibernate-dev] ORM progress: tricky branch state

[Vlad Mihalcea]

If 5.3 cannot take new features, it's better to branch it and have a 5.4
branch for the master until 6.0 is ready.

There are lots of interesting improvements that are provided via PRs or as
suggestions on  the forum, so it would be detrimental to our users to delay
those until 6.0 can be used in production.

Vlad

On Mon, 2 Jul 2018, 18:48 Sanne Grinovero, <sanne at hibernate.org> wrote:

> On Hibernate ORM we're currently having "master" branch essentially
> being a maintenance branch, aka master today is what's planned to be
> version 5.3.2.Final in some days, 5.3.3 later, etc..
>
> This is quite unusual, and it begs some extra attention: normally we'd
> start a new minor in master, so that PRs of any kind could be welcome
> in master, while specific, cherry-picked fixes are backported to the
> last maintained minors.
>
> This is not the case now and until we move on to a new minor or major
> we'll need to be particularly careful about what is allowed to be
> merged.
> I'm not pointing fingers to any specific commit, my concern is just
> raised by the high volume of changes being merged. They all look great
> individually but changes are not good at this point :)
>
> Not sure what to suggest to people wanting to contribute new features
> today; maybe hold as we assume the 6.0 work will be merged in master
> soon? Will be hard to say no to many reasonable requests though.
>
> Steve, do you think that the 6.0 merge could happen soon enough to not
> need any process changes in how  we deal with master?
>
> Thanks,
> Sanne
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>