Guess it helps if i give urls :)
http://in.relation.to/Bloggers/HibernatecoreRepoRename
On Wed 11 Jan 2012 11:53:55 AM CST, Steve Ebersole wrote:
> Discussion of the ramifications of renaming the repo. Seems pretty minor.
>
> On 01/10/2012 09:03 AM, Steve Ebersole wrote:
>> the jbott logging bot
Repo has been renamed, and 4.0 has been branched off.
On Wed 11 Jan 2012 02:54:10 PM CST, Steve Ebersole wrote:
> Guess it helps if i give urls :)
>
> http://in.relation.to/Bloggers/HibernatecoreRepoRename
>
>
> On Wed 11 Jan 2012 11:53:55 AM CST, Steve Ebersole wrote:
>> Discussion of the ramifi
http://in.relation.to/Bloggers/HibernateCore401Released
See also, http://in.relation.to/Bloggers/HibernatecoreRepoRename
Also, 4.0 will get branched today/tomorrow so we can start pushing work
for 4.1 development
--
st...@hibernate.org
http://hibernate.org
_
Discussion of the ramifications of renaming the repo. Seems pretty minor.
On 01/10/2012 09:03 AM, Steve Ebersole wrote:
> the jbott logging bot was not around today, so i just captured the
> discussion an have attached it here.
>
> Essentially:
> 1) 4.0.1 release on 4/11
> 2) after 4.0.1: (a) ren
I know, I've been keeping a track of it. I thought I had fixed the issue
yesterday. It's very very hard to replicate locally. I think it's cluster
formation related. I've added another barrier a few minutes ago to make sure
the cluster is formed before the tests are executed.
I'm pretty confide
We have been having intermittent failures with the hibernate-infinispan
module. Yesterday's upgrade to the latest Infinispan version seems to
exacerbate this condition; at least the CI builds are failing routinely now.
I think we either need to spend some time cleaning up whatever leads to
the
