+1, good idea. Thanks!
2018-01-09 14:46 GMT+01:00 Guillaume Smet :
> Hi,
>
> Now that we added some more value to the Bean Validation benchmark [1]
> (Marko converted them to JMH), I think it's time to move the repo to the
> Hibernate org.
>
> Anyone against it?
>
> FYI, it's Apache 2 licensed as
Hello,
TL;DR: I installed a plugin to prioritize Jenkins jobs, please let me know
if you notice anything wrong. Also, I will remove the Heavy Job plugin
soon, let me know if you're not okay with that.
I recently raised the issue on HipChat that some Jenkins builds are
triggered in batch, somethin
Hi,
On Wed, Jan 10, 2018 at 11:06 AM, Yoann Rodiere wrote:
>
> I hope we will be able to use this priority feature instead of the Heavy
> Job plugin (which allows to assign weights to jobs), and avoid concurrent
> builds completely. With the current setup, someone releasing his/her
> project will
Hi,
So I did the move.
And then I thought why not the beanvalidation organization?
I didn't think of it before as I'm not sure this benchmark will stay
totally HV agnostic but for now it is and it could probably stay this way.
If we want some HV specific things, we can still add a specific bench
On 10 January 2018 at 10:25, Guillaume Smet wrote:
> Hi,
>
> On Wed, Jan 10, 2018 at 11:06 AM, Yoann Rodiere wrote:
>>
>> I hope we will be able to use this priority feature instead of the Heavy
>> Job plugin (which allows to assign weights to jobs), and avoid concurrent
>> builds completely. Wit
Hello,
I've upgraded awestruct to version 0.5.7.
Except for the minification of our stylesheets it seems to work fine
but It would be nice if someone else can have a look at generate site
and confirm to me that's
OK to apply the changes in production.
On the same note, I've noticed that we are us
I had been wondering about that, too, but I felt for now it's better
located on the impl site (Hibernate org).
It'd definitely be nice for this to be a BV effort, but for that I'd also
like to get some feedback and input from others on the EG. My thinking was
to keep that discussion for the 2.1 li
> Let's not forget that many Apache projects take a week or two to
> perform a release, we all know of other projects needing months, so by
> the law of diminishing returns I don't think we should invest much
> more of out time to shave on the 10 minutes.. just spin up some extra
> nodes :)
+1
Just to clarify, The websites to check are:
http://staging.in.relation.to and http://staging.hibernate.org
Sorry, I forgot to add the links in the previous mail.
On Wed, Jan 10, 2018 at 11:08 AM, Davide D'Alto wrote:
> Hello,
> I've upgraded awestruct to version 0.5.7.
>
> Except for the minific
On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero
wrote:
> Some of our test suites used to take 2 hours to run (even 5 days some
> years ago); now you say waiting 20 minutes is not good enough? You'll
> have to optimise our code better :P
>
What I'm saying is that in the current setup, I don't w
Hi,
On Fri, Jan 5, 2018 at 4:24 PM, Steve Ebersole wrote:
> Yep, I know how long it takes to do a release - I've been doing them for
> almost 15 years ;)
>
> I'm not sure if you are agreeing or disagreeing about blogging every
> bugfix release. But anyway, Sanne asked what would help automate t
Thanks for taking care of that.
I clicked here and there, especially on the complex pages, and it looks
good to me.
Be careful when merging, we don't want the Corporate contributors page on
the public website yet.
Thanks!
--
Guillaume
On Wed, Jan 10, 2018 at 12:25 PM, Davide D'Alto
wrote:
>
Thanks,
I will only add the additional commits I made.
On Wed, Jan 10, 2018 at 11:45 AM, Guillaume Smet
wrote:
> Thanks for taking care of that.
>
> I clicked here and there, especially on the complex pages, and it looks good
> to me.
>
> Be careful when merging, we don't want the Corporate con
On 10 January 2018 at 11:33, Guillaume Smet wrote:
> On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero
> wrote:
>>
>> Some of our test suites used to take 2 hours to run (even 5 days some
>> years ago); now you say waiting 20 minutes is not good enough? You'll
>> have to optimise our code better
And in advance I say I would not be cool with you killing my jobs for your
job to run
On Wed, Jan 10, 2018 at 9:52 AM Sanne Grinovero wrote:
> On 10 January 2018 at 11:33, Guillaume Smet
> wrote:
> > On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero
> > wrote:
> >>
> >> Some of our test suites
I am going to delay 5.3.0.Beta1 until next week to investigate OSSRH
publishing. I noticed yesterday that Bintray has a 10G storage limit which
we would hit too quickly.
Feel free to add issues to Beta1, but only if you plan on having them done
by next week (1/17).
___
It would be nice to have
https://github.com/hibernate/hibernate-orm/pull/2092 in 5.3.0.Beta1, so
that we can start experimenting in Search :)
Just saw there's a conflict (again), I will rebase.
On Wed, 10 Jan 2018 at 17:14 Steve Ebersole wrote:
> I am going to delay 5.3.0.Beta1 until next week t
On Wed, Jan 10, 2018 at 5:00 PM, Steve Ebersole wrote:
> And in advance I say I would not be cool with you killing my jobs for your
> job to run
>
Yeah, that was my understanding.
I don't expect anyone to be cool with it.
___
hibernate-dev mailing lis
On Wed, Jan 10, 2018 at 4:50 PM, Sanne Grinovero
wrote:
> I'm confused now. AFAIK this has never been the case? I understand
> that the release process itself runs without running the tests, but
> I'd still run the tests by triggering a full build before.
> You made the example of the TCK and var
Yoann, yes, I will get that in. Honestly it would have even been in the
one today - the Bintray concern was just very last minute that I felt it
best to hold off for the week.
On Wed, Jan 10, 2018 at 10:18 AM Yoann Rodiere wrote:
> It would be nice to have
> https://github.com/hibernate/hiberna
I know ;)
Anyway I do agree that any release jobs should be given the highest
priority in the job queue
On Wed, Jan 10, 2018, 10:29 AM Guillaume Smet
wrote:
> On Wed, Jan 10, 2018 at 5:00 PM, Steve Ebersole
> wrote:
>
>> And in advance I say I would not be cool with you killing my jobs for
>>
Hi,
While reviewing old PRs we have in the ORM project, I stumbled on this one
about serializing the SessionFactory.
I created a new PR, rebased on top of the current master branch and all
tests are passing fine.
If anyone wants to take a look, this is the PR:
https://github.com/hibernate/hiber
The SessionFactory being Serialized outside the VM? Because otherwise it
is already "serializable" via VM serialization hooks
and org.hibernate.internal.SessionFactoryRegistry. And I'm not so
convinced we should support serializing it for "out of" VM use aside from
what we already do which assume
Hi Hilmer,
Welcome to the list and +1 to that constraint. I think it's a good idea
overall, will comment on the PR on some details as needed.
Cheers,
--Gunnar
2018-01-08 13:04 GMT+01:00 Guillaume Smet :
> Hi Hilmer,
>
> On Sat, Jan 6, 2018 at 9:10 PM, Hilmer Chona wrote:
>
> > I have created
As $subject. Please don't push anything to 5.1 branch.
Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
http://in.relation.to/2018/01/10/hibernate-orm-5111-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
26 matches
Mail list logo
