Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-17 Thread Sanne Grinovero
On 17 July 2015 at 10:07, Gunnar Morling wrote: > Interesting, so they'd really block the link from being shared due to the > broken author meta-data. And worse: you get strongly penalized in SEO terms. Next we should add valid microdata. -- Sanne > > 2015-07-17 11:03 GMT+02:00 Sanne Grinovero

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-17 Thread Gunnar Morling
Interesting, so they'd really block the link from being shared due to the broken author meta-data. 2015-07-17 11:03 GMT+02:00 Sanne Grinovero : > G+ link sharing works now. Thanks Gunnar and Emmanuel for the quick > "meta fix" WEBSITE-380! > > Cheers, > Sanne > > On 16 July 2015 at 11:37, Sanne G

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-17 Thread Sanne Grinovero
G+ link sharing works now. Thanks Gunnar and Emmanuel for the quick "meta fix" WEBSITE-380! Cheers, Sanne On 16 July 2015 at 11:37, Sanne Grinovero wrote: > Ah, that helps; I hadn't understood you were talking about the "share > link" feature. > > I could reproduce the problem now; it seems one

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-16 Thread Sanne Grinovero
Ah, that helps; I hadn't understood you were talking about the "share link" feature. I could reproduce the problem now; it seems one probable cause is the in.relation.to website to contain invalid microdata. I wanted to improve the microdata anyway so I'll have a look this evening. Thanks, Sanne

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-16 Thread Gunnar Morling
But his this a real "shared link"? This does not work for me with the CR2 post, also not on my personal account. 2015-07-16 12:13 GMT+02:00 Sanne Grinovero : > I had no problems have anyone post on g+ and link to in.relation.to: > https://plus.google.com/101574584265991227194/posts/AsM3PUHwLBX >

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-16 Thread Sanne Grinovero
I had no problems have anyone post on g+ and link to in.relation.to: https://plus.google.com/101574584265991227194/posts/AsM3PUHwLBX Is there some limitation on the Hibernate.org g+ specifically? On 15 July 2015 at 17:20, Steve Ebersole wrote: > Gunnar mentioned having the same problem. On the

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-15 Thread Steve Ebersole
Gunnar mentioned having the same problem. On the Hibernate.org g+ page, if I try to add a post that contains a link to our in.relation.to domain, it will not let me create the post. On Wed, Jul 15, 2015 at 10:47 AM Sanne Grinovero wrote: > Could you elaborate please? You could not link to our d

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-15 Thread Sanne Grinovero
Could you elaborate please? You could not link to our domain? On 15 Jul 2015 15:33, "Steve Ebersole" wrote: > FWIW, I just tried to use the new in.relation.to url in g+ post but it was > not accepted. Google did not say anything specific about why it was not > accepted. > > > On Thu, Jul 9, 2015

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-15 Thread Steve Ebersole
FWIW, I just tried to use the new in.relation.to url in g+ post but it was not accepted. Google did not say anything specific about why it was not accepted. On Thu, Jul 9, 2015 at 11:25 AM andrea boriero wrote: > I have just modified the post, need only to push. > Emmanuel can you just take ca

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-09 Thread andrea boriero
I have just modified the post, need only to push. Emmanuel can you just take care of mails, g+ etc? On 9 July 2015 at 17:16, Emmanuel Bernard wrote: > I’ll do this. > > > > On 09 Jul 2015, at 15:35, Steve Ebersole wrote: > > > > Too late now. I am off for some hiking / camping with my fiancé.

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-09 Thread Emmanuel Bernard
I’ll do this. > On 09 Jul 2015, at 15:35, Steve Ebersole wrote: > > Too late now. I am off for some hiking / camping with my fiancé. > > If someone could do me a favor and take the blog post from staging (or > better yet, the post from Github release) and make a post on production and > finis

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-09 Thread Steve Ebersole
Too late now. I am off for some hiking / camping with my fiancé. If someone could do me a favor and take the blog post from staging (or better yet, the post from Github release) and make a post on production and finish announcing the release (email, g+, etc) I would really appreciate it. On Wed,

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-08 Thread Hardy Ferentschik
> As I said, I had trouble writing this blog in the new asciidoctor stuff. I > had some trouble getting ruby etal set up locally. Sanne had mentioned > that I could just push to staging branch and CI would automatically build > it for me and I could check it that way. Well the CI job clearly saw

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-08 Thread Hardy Ferentschik
Hi, On Wed, Jul 08, 2015 at 07:17:07PM +, Steve Ebersole wrote: > As I said, I had trouble writing this blog in the new asciidoctor stuff. I > had some trouble getting ruby etal set up locally Can you provide any more info than that? I am happy to help you setting this up, but I need some m

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-08 Thread Steve Ebersole
Wow, now it shows up. Like almost an hour later. On Wed, Jul 8, 2015 at 2:17 PM Steve Ebersole wrote: > As I said, I had trouble writing this blog in the new asciidoctor stuff. > I had some trouble getting ruby etal set up locally. Sanne had mentioned > that I could just push to staging branch

Re: [hibernate-dev] Second candidate release for Hibernate ORM 5.0

2015-07-08 Thread Steve Ebersole
As I said, I had trouble writing this blog in the new asciidoctor stuff. I had some trouble getting ruby etal set up locally. Sanne had mentioned that I could just push to staging branch and CI would automatically build it for me and I could check it that way. Well the CI job clearly saw my chan