Re: [hibernate-dev] 5.3.0 release tomorrow

2018-02-01 Thread Steve Ebersole
Starting release

On Thu, Feb 1, 2018 at 7:42 AM Vlad Mihalcea 
wrote:

> Thanks,
>
> I was having some Pull Requests which I pushed to 5.2.13 and wanted to
> have them in 5.3 as well.
>
> I will add them now.
>
> Vlad
>
> On Thu, Feb 1, 2018 at 3:34 PM, Steve Ebersole 
> wrote:
>
>> If it's stuff that's ready to go, go for it.  I'll send out an email when
>> I'm ready to start.
>>
>> On Thu, Feb 1, 2018, 7:28 AM Vlad Mihalcea 
>> wrote:
>>
>>> Hi Steve,
>>>
>>> Is it ok to commit on the master branch today or should we wait for 5.3
>>> to be released?
>>>
>>> Vlad
>>> On Thu, Feb 1, 2018 at 4:03 AM, Steve Ebersole 
>>> wrote:
>>>
 I am waiting until I hear back from Joel from Sonatype regarding
 disabling
 the JBoss Nexus -> OSSRH sync for ORM artifacts before I can release.

 On Wed, Jan 31, 2018 at 10:06 AM Guillaume Smet <
 guillaume.s...@gmail.com>
 wrote:

>>>
 > On Wed, Jan 31, 2018 at 4:54 PM, Steve Ebersole 
 > wrote:
 >
 >> Yes, I agree.  As it is, it is very likely that in 2 weeks we will
 have
 >> ORM 5.3.0.CR1.  So even if you did do a OGM release at that time we
 are
 >> going to be limited in what exactly we can change if we find changes
 are
 >> needed.
 >>
 >> Interestingly this goes back to earlier discussions about "release
 >> early/often" for the purpose of identifying regressions.  Granted
 there
 >> y'all were talking about 5.2, but the same happens here from the ORM
 >> perspective in 5.3.  We need to not be dragging version non-stable
 releases
 >> out as we continue to wait for +1's from all integrators (Search,
 OGM,
 >> Spring, etc).
 >>
 >
 > Yes, for a lot of reasons (good and bad) we were really bad with the
 ORM
 > 5.2 support in OGM.
 >
 > We are very aware of that and the idea is to not do that again :).
 >
 > We (probably Davide) will let you know about our progress soon.
 >
 > --
 > Guillaume
 >

>>> ___
 hibernate-dev mailing list
 hibernate-dev@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/hibernate-dev

>>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-02-01 Thread Steve Ebersole
If it's stuff that's ready to go, go for it.  I'll send out an email when
I'm ready to start.

On Thu, Feb 1, 2018, 7:28 AM Vlad Mihalcea  wrote:

> Hi Steve,
>
> Is it ok to commit on the master branch today or should we wait for 5.3 to
> be released?
>
> Vlad
> On Thu, Feb 1, 2018 at 4:03 AM, Steve Ebersole 
> wrote:
>
>> I am waiting until I hear back from Joel from Sonatype regarding disabling
>> the JBoss Nexus -> OSSRH sync for ORM artifacts before I can release.
>>
>> On Wed, Jan 31, 2018 at 10:06 AM Guillaume Smet > >
>> wrote:
>>
>
>> > On Wed, Jan 31, 2018 at 4:54 PM, Steve Ebersole 
>> > wrote:
>> >
>> >> Yes, I agree.  As it is, it is very likely that in 2 weeks we will have
>> >> ORM 5.3.0.CR1.  So even if you did do a OGM release at that time we are
>> >> going to be limited in what exactly we can change if we find changes
>> are
>> >> needed.
>> >>
>> >> Interestingly this goes back to earlier discussions about "release
>> >> early/often" for the purpose of identifying regressions.  Granted there
>> >> y'all were talking about 5.2, but the same happens here from the ORM
>> >> perspective in 5.3.  We need to not be dragging version non-stable
>> releases
>> >> out as we continue to wait for +1's from all integrators (Search, OGM,
>> >> Spring, etc).
>> >>
>> >
>> > Yes, for a lot of reasons (good and bad) we were really bad with the ORM
>> > 5.2 support in OGM.
>> >
>> > We are very aware of that and the idea is to not do that again :).
>> >
>> > We (probably Davide) will let you know about our progress soon.
>> >
>> > --
>> > Guillaume
>> >
>>
> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-02-01 Thread Vlad Mihalcea
Thanks,

I was having some Pull Requests which I pushed to 5.2.13 and wanted to have
them in 5.3 as well.

I will add them now.

Vlad

On Thu, Feb 1, 2018 at 3:34 PM, Steve Ebersole  wrote:

> If it's stuff that's ready to go, go for it.  I'll send out an email when
> I'm ready to start.
>
> On Thu, Feb 1, 2018, 7:28 AM Vlad Mihalcea 
> wrote:
>
>> Hi Steve,
>>
>> Is it ok to commit on the master branch today or should we wait for 5.3
>> to be released?
>>
>> Vlad
>> On Thu, Feb 1, 2018 at 4:03 AM, Steve Ebersole 
>> wrote:
>>
>>> I am waiting until I hear back from Joel from Sonatype regarding
>>> disabling
>>> the JBoss Nexus -> OSSRH sync for ORM artifacts before I can release.
>>>
>>> On Wed, Jan 31, 2018 at 10:06 AM Guillaume Smet <
>>> guillaume.s...@gmail.com>
>>> wrote:
>>>
>>
>>> > On Wed, Jan 31, 2018 at 4:54 PM, Steve Ebersole 
>>> > wrote:
>>> >
>>> >> Yes, I agree.  As it is, it is very likely that in 2 weeks we will
>>> have
>>> >> ORM 5.3.0.CR1.  So even if you did do a OGM release at that time we
>>> are
>>> >> going to be limited in what exactly we can change if we find changes
>>> are
>>> >> needed.
>>> >>
>>> >> Interestingly this goes back to earlier discussions about "release
>>> >> early/often" for the purpose of identifying regressions.  Granted
>>> there
>>> >> y'all were talking about 5.2, but the same happens here from the ORM
>>> >> perspective in 5.3.  We need to not be dragging version non-stable
>>> releases
>>> >> out as we continue to wait for +1's from all integrators (Search, OGM,
>>> >> Spring, etc).
>>> >>
>>> >
>>> > Yes, for a lot of reasons (good and bad) we were really bad with the
>>> ORM
>>> > 5.2 support in OGM.
>>> >
>>> > We are very aware of that and the idea is to not do that again :).
>>> >
>>> > We (probably Davide) will let you know about our progress soon.
>>> >
>>> > --
>>> > Guillaume
>>> >
>>>
>> ___
>>> hibernate-dev mailing list
>>> hibernate-dev@lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-02-01 Thread Vlad Mihalcea
Hi Steve,

Is it ok to commit on the master branch today or should we wait for 5.3 to
be released?

Vlad

On Thu, Feb 1, 2018 at 4:03 AM, Steve Ebersole  wrote:

> I am waiting until I hear back from Joel from Sonatype regarding disabling
> the JBoss Nexus -> OSSRH sync for ORM artifacts before I can release.
>
> On Wed, Jan 31, 2018 at 10:06 AM Guillaume Smet 
> wrote:
>
> > On Wed, Jan 31, 2018 at 4:54 PM, Steve Ebersole 
> > wrote:
> >
> >> Yes, I agree.  As it is, it is very likely that in 2 weeks we will have
> >> ORM 5.3.0.CR1.  So even if you did do a OGM release at that time we are
> >> going to be limited in what exactly we can change if we find changes are
> >> needed.
> >>
> >> Interestingly this goes back to earlier discussions about "release
> >> early/often" for the purpose of identifying regressions.  Granted there
> >> y'all were talking about 5.2, but the same happens here from the ORM
> >> perspective in 5.3.  We need to not be dragging version non-stable
> releases
> >> out as we continue to wait for +1's from all integrators (Search, OGM,
> >> Spring, etc).
> >>
> >
> > Yes, for a lot of reasons (good and bad) we were really bad with the ORM
> > 5.2 support in OGM.
> >
> > We are very aware of that and the idea is to not do that again :).
> >
> > We (probably Davide) will let you know about our progress soon.
> >
> > --
> > Guillaume
> >
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread Steve Ebersole
I am waiting until I hear back from Joel from Sonatype regarding disabling
the JBoss Nexus -> OSSRH sync for ORM artifacts before I can release.

On Wed, Jan 31, 2018 at 10:06 AM Guillaume Smet 
wrote:

> On Wed, Jan 31, 2018 at 4:54 PM, Steve Ebersole 
> wrote:
>
>> Yes, I agree.  As it is, it is very likely that in 2 weeks we will have
>> ORM 5.3.0.CR1.  So even if you did do a OGM release at that time we are
>> going to be limited in what exactly we can change if we find changes are
>> needed.
>>
>> Interestingly this goes back to earlier discussions about "release
>> early/often" for the purpose of identifying regressions.  Granted there
>> y'all were talking about 5.2, but the same happens here from the ORM
>> perspective in 5.3.  We need to not be dragging version non-stable releases
>> out as we continue to wait for +1's from all integrators (Search, OGM,
>> Spring, etc).
>>
>
> Yes, for a lot of reasons (good and bad) we were really bad with the ORM
> 5.2 support in OGM.
>
> We are very aware of that and the idea is to not do that again :).
>
> We (probably Davide) will let you know about our progress soon.
>
> --
> Guillaume
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread Steve Ebersole
Yes, I agree.  As it is, it is very likely that in 2 weeks we will have ORM
5.3.0.CR1.  So even if you did do a OGM release at that time we are going
to be limited in what exactly we can change if we find changes are needed.

Interestingly this goes back to earlier discussions about "release
early/often" for the purpose of identifying regressions.  Granted there
y'all were talking about 5.2, but the same happens here from the ORM
perspective in 5.3.  We need to not be dragging version non-stable releases
out as we continue to wait for +1's from all integrators (Search, OGM,
Spring, etc).

Anyway, we'll hear what we hear in 2 weeks.

On Wed, Jan 31, 2018 at 9:49 AM Guillaume Smet 
wrote:

> On Wed, Jan 31, 2018 at 4:42 PM, Steve Ebersole 
> wrote:
>
>> The next time-box is in fact 2 weeks... :)
>>
>> But yes, OGM makes me a little nervous as as far as I know we have no
>> idea about that integration yet
>>
>
> We discussed it on Tuesday at our meeting.
>
> I think we can commit to getting your feedback on OGM in the next 2 weeks.
>
> Personally, I would like to have an OGM release supporting ORM 5.3 not
> long ago after the ORM 5.3 release, even if we don't have any new features.
>
> --
> Guillaume
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread Guillaume Smet
On Wed, Jan 31, 2018 at 4:42 PM, Steve Ebersole  wrote:

> The next time-box is in fact 2 weeks... :)
>
> But yes, OGM makes me a little nervous as as far as I know we have no idea
> about that integration yet
>

We discussed it on Tuesday at our meeting.

I think we can commit to getting your feedback on OGM in the next 2 weeks.

Personally, I would like to have an OGM release supporting ORM 5.3 not long
ago after the ORM 5.3 release, even if we don't have any new features.

-- 
Guillaume
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread Steve Ebersole
The next time-box is in fact 2 weeks... :)

Hopefully we have these JPA TCK challenges resolved by then and can do CR
then.  So yes, please have feedback by then.  Yoann and I have been working
on Search and ORM 5.3 (at least parts) so I think that will work out fine.
But yes, OGM makes me a little nervous as as far as I know we have no idea
about that integration yet


On Wed, Jan 31, 2018 at 9:22 AM Guillaume Smet 
wrote:

> I would say let's go for Beta2. We are not in a hurry considering the
> challenges still pending so no need to rush in the CR phase.
>
> On the NoORM side:
> - Search - Yoann has prepared a PR with the 5.3 support so we should be OK
> on this side. 5.9 will be tagged early next week and we'll release an alpha
> of 5.10 for OGM consumption.
> - OGM - Davide is going to release OGM 5.2 (still with ORM 5.1) early next
> week, then we will merge the ORM 5.2 support that is pending for quite some
> time (the PR is ready, just waiting for the 5.2 release) and we will
> experiment with the 5.3 support on top of that. I don't expect many issues
> as it's not a step as big as 5.1 -> 5.2.
>
> So you can expect some feedback from us in the next 2 weeks.
>
> On Wed, Jan 31, 2018 at 4:11 PM, Chris Cranford 
> wrote:
>
>> I have no strong preference either way.
>>
>> On 01/30/2018 05:00 PM, Steve Ebersole wrote:
>> > Wanted to remind everyone that tomorrow is the next time-boxed release
>> for
>> > 5.3.
>> >
>> > I wanted to get everyone's opinions about the version number, whether
>> this
>> > should be Beta2 or CR1.  IMO It depends how you view the remaining
>> > challenges with the JPA TCK, with CR1 being the optimistic view.
>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread Guillaume Smet
I would say let's go for Beta2. We are not in a hurry considering the
challenges still pending so no need to rush in the CR phase.

On the NoORM side:
- Search - Yoann has prepared a PR with the 5.3 support so we should be OK
on this side. 5.9 will be tagged early next week and we'll release an alpha
of 5.10 for OGM consumption.
- OGM - Davide is going to release OGM 5.2 (still with ORM 5.1) early next
week, then we will merge the ORM 5.2 support that is pending for quite some
time (the PR is ready, just waiting for the 5.2 release) and we will
experiment with the 5.3 support on top of that. I don't expect many issues
as it's not a step as big as 5.1 -> 5.2.

So you can expect some feedback from us in the next 2 weeks.

On Wed, Jan 31, 2018 at 4:11 PM, Chris Cranford  wrote:

> I have no strong preference either way.
>
> On 01/30/2018 05:00 PM, Steve Ebersole wrote:
> > Wanted to remind everyone that tomorrow is the next time-boxed release
> for
> > 5.3.
> >
> > I wanted to get everyone's opinions about the version number, whether
> this
> > should be Beta2 or CR1.  IMO It depends how you view the remaining
> > challenges with the JPA TCK, with CR1 being the optimistic view.
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread Chris Cranford
I have no strong preference either way.

On 01/30/2018 05:00 PM, Steve Ebersole wrote:
> Wanted to remind everyone that tomorrow is the next time-boxed release for
> 5.3.
>
> I wanted to get everyone's opinions about the version number, whether this
> should be Beta2 or CR1.  IMO It depends how you view the remaining
> challenges with the JPA TCK, with CR1 being the optimistic view.
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread andrea boriero
having a Beta2 release is fine also to me

On 31 January 2018 at 10:26, Sanne Grinovero  wrote:

> I would suggest a Beta2, as we were hoping to still do some work on
> it. No strong take though, as far as I know our pending work is
> optional / low impact:
>  A. produce the feature packs in ORM
>  B. test OGM integration
>
> Status of these:
>
> A#
> The feature packs have low impact on ORM's risk and quality, although
> it would be nice to be able to test the feature packs "as released"
> from ORM within Search and OGM.
> It requires a second Gradle plugin; Andrea created a first POC last
> week, but we still need some work on it, release it and then have the
> ORM build use it.
> Finally we'll need to update the documentation and guides to explain
> to users how to consume it.
>
> B#
> The OGM integration is a bit late; we should be able to verify it next
> week. We didn't start converting OGM into feature packs; that would
> take even longer but I guess we can regard this one as optional.
>
> All of this could be done in a CR1 if you see reasons to accelerate,
> I'd just suggest a preference for a little more time.
>
> Thanks,
> Sanne
>
>
> On 30 January 2018 at 22:00, Steve Ebersole  wrote:
> > Wanted to remind everyone that tomorrow is the next time-boxed release
> for
> > 5.3.
> >
> > I wanted to get everyone's opinions about the version number, whether
> this
> > should be Beta2 or CR1.  IMO It depends how you view the remaining
> > challenges with the JPA TCK, with CR1 being the optimistic view.
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-31 Thread Sanne Grinovero
I would suggest a Beta2, as we were hoping to still do some work on
it. No strong take though, as far as I know our pending work is
optional / low impact:
 A. produce the feature packs in ORM
 B. test OGM integration

Status of these:

A#
The feature packs have low impact on ORM's risk and quality, although
it would be nice to be able to test the feature packs "as released"
from ORM within Search and OGM.
It requires a second Gradle plugin; Andrea created a first POC last
week, but we still need some work on it, release it and then have the
ORM build use it.
Finally we'll need to update the documentation and guides to explain
to users how to consume it.

B#
The OGM integration is a bit late; we should be able to verify it next
week. We didn't start converting OGM into feature packs; that would
take even longer but I guess we can regard this one as optional.

All of this could be done in a CR1 if you see reasons to accelerate,
I'd just suggest a preference for a little more time.

Thanks,
Sanne


On 30 January 2018 at 22:00, Steve Ebersole  wrote:
> Wanted to remind everyone that tomorrow is the next time-boxed release for
> 5.3.
>
> I wanted to get everyone's opinions about the version number, whether this
> should be Beta2 or CR1.  IMO It depends how you view the remaining
> challenges with the JPA TCK, with CR1 being the optimistic view.
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


Re: [hibernate-dev] 5.3.0 release tomorrow

2018-01-30 Thread Scott Marlow
On Tue, Jan 30, 2018 at 11:00 PM, Steve Ebersole 
wrote:

> Wanted to remind everyone that tomorrow is the next time-boxed release for
> 5.3.
>
> I wanted to get everyone's opinions about the version number, whether this
> should be Beta2 or CR1.  IMO It depends how you view the remaining
> challenges with the JPA TCK, with CR1 being the optimistic view.
>

I like Beta2 better but if you need to move on, CR1 would be okay as a JPA
2.2 preview, as long as we later release 5.3.1 with any further changes
that are needed (we still have to also pass the EE TCK).



> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


[hibernate-dev] 5.3.0 release tomorrow

2018-01-30 Thread Steve Ebersole
Wanted to remind everyone that tomorrow is the next time-boxed release for
5.3.

I wanted to get everyone's opinions about the version number, whether this
should be Beta2 or CR1.  IMO It depends how you view the remaining
challenges with the JPA TCK, with CR1 being the optimistic view.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev