Re: [hibernate-dev] hibernate.org ORM release series page

[Yoann Rodiere]

>  Is this going to be as simple as adding a
new layout (`project-releases-series-bintray.html.haml`?) and using that as
the layout for http://hibernate.org/orm/releases/5.3/ ?

It should be, yes. Though a better option might be to introduce switches
based on the project, especially if you only want to change the "Maven,
gradle..." section and the URL for specific releases. That way, the other
parts of the page would still stay the same.

Anyway... We also have issues with the Nexus links, so I'll try to fix both
issues, push to staging and report here. Then you can iterate on what I
started (wording, ...).

On Fri, 2 Feb 2018 at 02:26 Steve Ebersole  wrote:

> Now that I've moved ORM publishing to Bintray some of the layout of
> hibernate.org in regards to releases is not-so-nice.  Most of this comes
> into play in the `project-releases-series.html.haml` file use as the layout
> for these "series" pages.
>
> Specifically:
>
>1. Some of the text injected is just wrong.  "Maven artifacts of
>Hibernate ORM are published to Maven Central and to the JBoss Maven
>Repository. Refer to the Maven Getting Started guide on the Jboss Wiki
> for
>more information on how to configure Maven."  Most of that is now
>inaccurate.
>2. One of the niceties of moving to Bintray is having a singular URL to
>refer to the artifacts included in the release.  E.g.
>https://bintray.com/hibernate/artifacts/hibernate-orm/5.3.0.Beta2.  The
>layout here though is set up to list out each artifact individually.
>
> I'd like to change this for ORM 5.3 moving forward such that the "Maven,
> Gradle..." section simply points to the Bintray URL, as well as changing
> that text to be ore accurate.  Is this going to be as simple as adding a
> new layout (`project-releases-series-bintray.html.haml`?) and using that as
> the layout for http://hibernate.org/orm/releases/5.3/ ?
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
-- 
Yoann Rodiere
yo...@hibernate.org / yrodi...@redhat.com
Software Engineer
Hibernate NoORM team
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] hibernate.org ORM release series page

[Steve Ebersole]

Now that I've moved ORM publishing to Bintray some of the layout of
hibernate.org in regards to releases is not-so-nice.  Most of this comes
into play in the `project-releases-series.html.haml` file use as the layout
for these "series" pages.

Specifically:

   1. Some of the text injected is just wrong.  "Maven artifacts of
   Hibernate ORM are published to Maven Central and to the JBoss Maven
   Repository. Refer to the Maven Getting Started guide on the Jboss Wiki for
   more information on how to configure Maven."  Most of that is now
   inaccurate.
   2. One of the niceties of moving to Bintray is having a singular URL to
   refer to the artifacts included in the release.  E.g.
   https://bintray.com/hibernate/artifacts/hibernate-orm/5.3.0.Beta2.  The
   layout here though is set up to list out each artifact individually.

I'd like to change this for ORM 5.3 moving forward such that the "Maven,
Gradle..." section simply points to the Bintray URL, as well as changing
that text to be ore accurate.  Is this going to be as simple as adding a
new layout (`project-releases-series-bintray.html.haml`?) and using that as
the layout for http://hibernate.org/orm/releases/5.3/ ?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] NoORM IRC meeting minutes

[Guillaume Smet]

Hi,

Just happened to me that I forgot to send the email with the minutes of
this week's NoORM meeting.

Here they are:
15:55 < jbott> Meeting ended Tue Jan 30 14:55:28 2018 UTC.  Information
about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:55 < jbott> Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/hibernate-dev.2018-01-30-14.00.html
15:55 < jbott> Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/hibernate-dev.2018-01-30-14.00.txt
15:55 < jbott> Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/hibernate-dev.2018-01-30-14.00.log.html

-- 
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

[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

[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

[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] Minor changes to the website

[Vlad Mihalcea]

Great job Guillaume,

It looks awesome.

Vlad

On Wed, Jan 31, 2018 at 2:15 PM, Guillaume Smet 
wrote:

> Hi,
>
> Just so you know, I just made a few minor changes to the website:
> - in the Releases dymanic submenu, you now have a label stating "latest
> stable"/"development" to make it clearer what the versions are (it's
> especially useful at this point of the ORM development for instance as 5.3
> is the latest but not yet considered stable)
> - I made the Documentation entry menu of ORM dynamic with a submenu
> following the same principles as for Releases. It avoids going to the
> latest then using the dropdown at the top (I kept the dropdown anyway)
>
> In passing, I also added a placeholder page for the ORM 5.3 doc stating it
> will be available soon.
>
> HTH
>
> --
> 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] Should EntityManager#refresh retain an existing lock?

[Vlad Mihalcea]

Hi Gail,

Steve is right. Database locks cannot be released unless you end the
transaction and that's how it works on any RDBMS, either in 2PL Mode or
MVCC.

As for optimistic locks:

1. LockModeType.OPTIMISTIC

The check is done at the end of the end of the transaction. Refresh will
only update the version, but the check should still be done so we should
not probably switch to LockModeTypeNONE.

2. OPTIMISTIC_FORCE_INCREMENT,

This one triggers a version increment in a different entity, so it should
not be affected by the refresh of our entity.

Vlad

On Thu, Feb 1, 2018 at 1:12 AM, Gail Badner  wrote:

> OK, sounds good.
>
> Thanks,
> Gail
>
> On Wed, Jan 31, 2018 at 2:38 PM, Steve Ebersole 
> wrote:
>
> > It is possible to call EntityManager#lock(Object entity, LockModeType
> >> lockMode) with a lower-level lock, but that request will be ignored.
> >> Hibernate will only upgrade a lock.
> >>
> >
> > Sure, this is in keeping with most (all?) databases - a transaction can
> > only acquire more restrictive locks.
> >
> >
> >
> >> I think that clarifies retaining the same lock-level for the entity when
> >> calling EntityManager#refresh(Object entity).
> >>
> >> If no one has any comments that disagree with this in the next couple of
> >> days, I'll go with that.
> >>
> >
> > That's the correct handling.
> >
> >
> ___
> 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

[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