Sanne, all,
Could we please drop the 5.5 branch in the upstream repo. It matches
exactly master (apart from the POM versions), so there is really no
good reason to have it at this point IMHO.
Let's do branches when they actually become necessary. In this case,
work meant only for 5.6 but not for
Reference https://hibernate.atlassian.net/browse/HHH-10242
I need to make another change in HCANN and pull that new version into ORM.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
At the moment Hibernate builds all of the Loaders that derive from
batchsize when the SessionFactory is built. So practically speaking you'd
have to account for that change in design.
But in general the idea would be ok.
On Wed, Nov 4, 2015 at 12:05 PM Vlad Mihalcea
wrote:
> Hi,
>
> I was bro
Hi,
I was browsing the Hibernate code and realized that the Batch/Non-Batch
decision is taken based on the value of the "hibernate.jdbc.batch_size"
SessionFactory configuration.
Wouldn't be more flexible if we allow the Session to have a setBathSize(int
size) method to override the batching config
On 4 November 2015 at 16:01, Steve Ebersole wrote:
> That would still put 5.0.5 in the middle of winter break.
>
> Probably we should schedule that for a 3 week timebox too. So:
>
> 5.0.4 -> November 18th
> 5.0.5 -> December 9th
> 5.0.6 -> January 6th (back to normal 4 week timebox)
>
>
>> I gene
That would still put 5.0.5 in the middle of winter break.
Probably we should schedule that for a 3 week timebox too. So:
- 5.0.4 -> November 18th
- 5.0.5 -> December 9th
- 5.0.6 -> January 6th (back to normal 4 week timebox)
I generally prefer shorter cycles
>
I agree, to a point. Bu
+1
I generally prefer shorter cycles
On Wed, 4 Nov 2015 06:11 andrea boriero wrote:
> I vote for November 18
> On 3 Nov 2015 18:36, "Steve Ebersole" wrote:
>
> > Keeping up with the 4 week timebox for 5.0 bugfix releases unfortunately
> > puts them on bad days with the upcoming holidays.
> >
>
Hi,
> This ties in with an uneasiness that has been growing on me tbh... We have
> too many places users have to look for potential information. The
> website, the JBoss wiki, the GitHub wiki, README.mds, CONTRIBUTING.mds.
> It's hard to keep straight :)
That has always been my concern.
> Ide
