[hibernate-dev] Regarding release versioning

[Steve Ebersole]

Sanne, you just said it.. the reason you did not test with 5.2 before it
was released is time.  Me doing a CR release does not change that.  The
stuff that "bit you" in 5.2 was available for testing for well over a month
prior to releasing 5.2.  And it's not like 5.2 was released without
discussion; heck we even pushed it back a few times to get a few extras
in.  All discussed on the dev list.

On Wed, Jun 8, 2016 at 7:55 AM Sanne Grinovero <sanne at hibernate.org> wrote:

> +1
>
> I've also hit some incompatible API changes which I only figured out
> too late (when attempting to upgrade Hibernate Search).
>
> I could have pre-tested snapshot builds but didn't have time for that
> - and didn't expect 5.2 to be released without a Beta period, or I
> would have made time for that.
>
>
> On 8 June 2016 at 08:09, Vlad Mihalcea <mihalcea.vlad at gmail.com> wrote:
> > Hi,
> >
> > I have seen the frustration from the Spring Data team trying to keep up
> > with our code changes that break their integrations,
> > and I was wondering if we should use some Release candidates prior to
> > releasing a start of a branch, even if it's a minor one.
> > This way, instead of 5.2.0, we could release 5.2.0.RC1 or something like
> > that to mark it as an intermediary release that's aimed for early
> > adopters/integrators.
> >
> > Do you think this is feasible or is there something to prevent us from
> > doing this?
> >
> > Vlad
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>