[hibernate-dev] ORM - HHH-12332 - Releasing a 5.2.15 quickly?

[andrea boriero]

nothing against reverting the PR that caused this issue.

On 6 March 2018 at 10:57, Guillaume Smet <guillaume.smet at gmail.com> wrote:

> Hi,
>
> So, AFAICS, Andrea found another failing case for the new PR.
>
> I would vote for reverting the original patch [
> https://hibernate.atlassian.net/browse/HHH-11544] for now and let
> Christian the time to think of a proper fix. I'm a bit worried we will miss
> something if we try to find a fix in a hurry.
>
> AFAICS, the original issue was a bit of a corner case so better get the
> other more common cases working.
>
> Anyone against reverting the original patch? Christian?
>
> --
> Guillaume
>
> On Mon, Mar 5, 2018 at 11:16 PM, Guillaume Smet <guillaume.smet at gmail.com>
> wrote:
>
>> Just so that nobody misses it, Christian pushed a PR here:
>> https://github.com/hibernate/hibernate-orm/pull/2180 .
>>
>> Will require someone more familiar with ORM than me to review it :).
>>
>> Thanks.
>>
>> On Mon, Mar 5, 2018 at 7:54 PM, Gail Badner <gbadner at redhat.com> wrote:
>>
>>> +1 to a quick release, with a partial solution if necessary.
>>>
>>> On Mon, Mar 5, 2018 at 7:28 AM, Steve Ebersole <steve at 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 at 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 at gmail.com> wrote:
>>> > >
>>> > > > On 03/05/2018 08:26 AM, Sanne Grinovero wrote:
>>> > > > > On 5 March 2018 at 12:27, Guillaume Smet <
>>> guillaume.smet at 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 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
>>> > >
>>> > _______________________________________________
>>> > 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
>>>
>>
>>
>