Gunnar mentioned having the same problem. On the
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 <sanne(a)hibernate.org>
wrote:
Could you elaborate please? You could not link to our domain?
On 15 Jul 2015 15:33, "Steve Ebersole" <steve(a)hibernate.org> 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 at 11:25 AM andrea boriero <dreborier(a)gmail.com>
> wrote:
>
> > 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 <emmanuel(a)hibernate.org>
> wrote:
> >
> >> I’ll do this.
> >>
> >>
> >> > On 09 Jul 2015, at 15:35, Steve Ebersole <steve(a)hibernate.org>
> 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
> >> > finish announcing the release (email, g+, etc) I would really
> >> appreciate it.
> >> >
> >> > On Wed, Jul 8, 2015, 4:12 PM Hardy Ferentschik
<hardy(a)hibernate.org>
> >> 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 and CI would
automatically
> >> build
> >> >>> it for me and I could check it that way. Well the CI job
clearly
> saw
> >> my
> >> >>> change and initiated a build[1]. The staging build succeeded,
but
> my
> >> >> post
> >> >>> was never displayed on the staging.in.relation.to site.
> >> >>
> >> >> I just did two test builds and in both cases the changes were
> visible
> >> >> directly
> >> >> after the CI build finished. I would say try again and if you see
> the
> >> same
> >> >> problem
> >> >> again we take a closer look.
> >> >>
> >> >> --Hardy
> >> >>
> >> > _______________________________________________
> >> > hibernate-dev mailing list
> >> > hibernate-dev(a)lists.jboss.org
> >> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>
> >>
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev(a)lists.jboss.org
> >>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>
> >
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev