[hibernate-dev] [OGM] Doing a 5.0.1 release?

2016-06-24 Thread Gunnar Morling
Hi, I noticed there is a 5.0.1 version in JIRA for OGM, and a handful of issues are assigned to it. Do we still plan to do such 5.0.1, or is everyone focused on the first preview for 5.1 right now? There is one interesting issue in 5.0.1 which alone I'd find worth releasing: OGM-828 ("Need to lis

Re: [hibernate-dev] [OGM] Doing a 5.0.1 release?

2016-06-24 Thread Sanne Grinovero
+1 keep those releases coming! and yes those fixes need to be made available better sooner than later. On 24 Jun 2016 09:14, "Gunnar Morling" wrote: > Hi, > > I noticed there is a 5.0.1 version in JIRA for OGM, and a handful of issues > are assigned to it. Do we still plan to do such 5.0.1, or is

Re: [hibernate-dev] [OGM] Doing a 5.0.1 release?

2016-06-24 Thread Davide D'Alto
Sounds good to me Davide On Fri, Jun 24, 2016 at 10:57 AM, Sanne Grinovero wrote: > +1 keep those releases coming! > and yes those fixes need to be made available better sooner than later. > On 24 Jun 2016 09:14, "Gunnar Morling" wrote: > >> Hi, >> >> I noticed there is a 5.0.1 version in JIRA

Re: [hibernate-dev] [OGM] Doing a 5.0.1 release?

2016-06-24 Thread Gunnar Morling
Cool; Anyone volunteering for doing the release? 2016-06-24 11:59 GMT+02:00 Davide D'Alto : > Sounds good to me > > Davide > > On Fri, Jun 24, 2016 at 10:57 AM, Sanne Grinovero > wrote: > > +1 keep those releases coming! > > and yes those fixes need to be made available better sooner than later.

Re: [hibernate-dev] HIbernate ORM CI builds

2016-06-24 Thread Steve Ebersole
I definitely want it run regularly (i.e. not "just before a release"). I'd be ok with it being nightly. That's why I asked in the first place. Everyone who responded +1'd to it being on-each-push. I really don't care. I tend to agree it should be nightly, but I only get one vote :) So the one

Re: [hibernate-dev] 6.0 - Type redesign

2016-06-24 Thread Steve Ebersole
I worked on this some more today and wanted to pass along a few high-points I started to see emerge... The idea of "Type scoping" is very important and central. The basic idea is to have a single point for the creation and caching of Type instances. Specifically this Scope would define just 2 met

Re: [hibernate-dev] HIbernate ORM CI builds

2016-06-24 Thread Sanne Grinovero
On 24 June 2016 at 16:40, Steve Ebersole wrote: > I definitely want it run regularly (i.e. not "just before a release"). I'd > be ok with it being nightly. That's why I asked in the first place. > Everyone who responded +1'd to it being on-each-push. I really don't care. > I tend to agree it sh

Re: [hibernate-dev] HIbernate ORM CI builds

2016-06-24 Thread Steve Ebersole
That's it, thanks! On Fri, Jun 24, 2016 at 11:13 AM Sanne Grinovero wrote: > On 24 June 2016 at 16:40, Steve Ebersole wrote: > > I definitely want it run regularly (i.e. not "just before a release"). > I'd > > be ok with it being nightly. That's why I asked in the first place. > > Everyone who

Re: [hibernate-dev] 6.0 - Type redesign

2016-06-24 Thread Gunnar Morling
Steve, I still need to look at the wiki page and will give more detailed feedback on some parts of it. One general thing coming to mind though is how support for OGM could be improved. On first thought I'd say the "Java side" of Type might stay as is, but the "SQL side" (or "datastore side") and

Re: [hibernate-dev] 6.0 - Type redesign

2016-06-24 Thread Steve Ebersole
This is all part of the to-be-decided read/write part of the new Type contract. I propose, as discussed in the wiki, that we have Type return ValueExtractor and ValueBinder for read/write. So assuming that is there... One possible answer to your story is that OGM as a SQM interpreter and Metamod