On Tue, Jun 5, 2018 at 3:38 PM, Luis Barreiro wrote:
> My reading on that javadoc is that you only get the transformation once
> (the first time that a class is loaded) and after that, if it's used by
> other PUs, it may not get the transformations those PUs specify.
>
We added TRACE logging
+1.
Unless there will be some serious issues that call for a 5.2.19 release, we
should focus on 5.3.
Vlad
On Wed, Jun 6, 2018 at 3:45 PM, Steve Ebersole wrote:
> +1 to stopping 5.2 releases.
>
> On Wed, Jun 6, 2018 at 7:40 AM Guillaume Smet
> wrote:
>
> > On Tue, Jun 5, 2018 at 10:33 PM Gail
I'm fine postponing the release for another week or 2 if that helps,
Christian.
On 06/06/2018 08:26 AM, Guillaume Smet wrote:
> On Tue, Jun 5, 2018 at 10:33 PM Gail Badner wrote:
>
>> Chris mentioned that he is planning to release 5.2.18 on Thursday.
>>
> It would be nice if we could get
>
+1 to stopping 5.2 releases.
On Wed, Jun 6, 2018 at 7:40 AM Guillaume Smet
wrote:
> On Tue, Jun 5, 2018 at 10:33 PM Gail Badner wrote:
>
> > Chris mentioned that he is planning to release 5.2.18 on Thursday.
> >
>
> It would be nice if we could get
>
On Tue, Jun 5, 2018 at 10:33 PM Gail Badner wrote:
> Chris mentioned that he is planning to release 5.2.18 on Thursday.
>
It would be nice if we could get
https://hibernate.atlassian.net/browse/HHH-12645 fixed before releasing
5.2.18, considering it's a regression introduced after 5.2.13. If we
On Wed, Jun 6, 2018 at 1:29 PM Sanne Grinovero wrote:
> I don't know about others but I didn't make changes on JIRA in a long
> time - or I'd normally share actions here.
>
It might also be due to a JIRA upgrade as they did quite a lot of changes.
Anyway, we are back on track now.
--
On 6 June 2018 at 12:04, Guillaume Smet wrote:
> On Wed, Jun 6, 2018 at 12:57 PM Sanne Grinovero wrote:
>>
>> Just curious, did that really work consistently?
>
>
> Well, it works consistently as in if your issue is in the "Pull request
> sent" status, the issue is considered "In progress".
>
>
On Wed, Jun 6, 2018 at 12:57 PM Sanne Grinovero wrote:
> Just curious, did that really work consistently?
>
Well, it works consistently as in if your issue is in the "Pull request
sent" status, the issue is considered "In progress".
This status is associated with the explicit action "Link to
Just curious, did that really work consistently?
As far as I know, the JIRA integration was never really able to match
GitHub PR changes to JIRA issues reliably.
On 6 June 2018 at 11:37, Guillaume Smet wrote:
> Hi,
>
> A few months back, when an issue was in the "Pull request sent" status, it
>
Nice! I had noticed that, but didn't think further, assuming it would not
be configurable anyway.
Thanks for fixing it.
On Wed, 6 Jun 2018 at 12:44 Guillaume Smet wrote:
> Hi,
>
> A few months back, when an issue was in the "Pull request sent" status, it
> was considered "In progress" and
Hi,
A few months back, when an issue was in the "Pull request sent" status, it
was considered "In progress" and appeared here:
https://hibernate.atlassian.net/projects/HV/versions/3/tab/release-report-in-progress
.
This apparently got broken at some point (or someone changed it without
11 matches
Mail list logo
