+1 to a quick release, with a partial solution if necessary.
On Mon, Mar 5, 2018 at 7:28 AM, Steve Ebersole <steve(a)hibernate.org> wrote:
I agree that in general it is ok to cut a release with a partial
solution
in a case like this
On Mon, Mar 5, 2018 at 8:40 AM andrea boriero <andrea(a)hibernate.org>
wrote:
> If there are no objections I can manage a release as soon as a fix is
> ready.
>
> On 5 March 2018 at 14:20, Chris Cranford <crancran(a)gmail.com> wrote:
>
> > On 03/05/2018 08:26 AM, Sanne Grinovero wrote:
> > > On 5 March 2018 at 12:27, Guillaume Smet <guillaume.smet(a)gmail.com>
> > > wrote:
> > >> Hi, So far we had 4 duplicate reports of
> > >>
https://hibernate.atlassian.net/browse/HHH-12332 (so not counting
the
> > >> users having seen the bug and not opening a new one). I think this
> > >> issue qualifies as "we should really get a hotfix release
soon".
> > > +1 that would be nice, and the most effective way to prevent further
> > > noise and pain.
> > I also would agree.
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev