Re: http://www.groovy-lang.org/ down

It's indeed usually pretty flawless and effective. Now, I don't fully understand what the ASF is using, but it involved "DNS slaves", whatever that means. On Sun, May 22, 2016 at 10:25 PM, Jim Northrop < james.b.north...@googlemail.com> wrote: > Just did 2 DNS name changes this afternoon using

Re: http://www.groovy-lang.org/ down

Would love to see a mirror groovy doc.s site like say, groovy-lang.net so if one is down we have a spare. Doc.s publish would push to two targets but quite do-able. Sent from my iPad > On 22 May 2016, at 20:36, Mario Garcia wrote: > > Thanks for the explanation

Re: http://www.groovy-lang.org/ down

Just did 2 DNS name changes this afternoon using goDaddy and worked flawlessly with no changed required to my internal server. So i'm a bit puzzled why this should be a biggie  Sent from my iPad > On 22 May 2016, at 20:20, Guillaume Laforge wrote: > > And... it's back

Re: http://www.groovy-lang.org/ down

> On May 22, 2016, at 11:20 AM, Guillaume Laforge wrote: > > And... it's back now! YAY! > > Sorry again for the inconvenience, but this was really beyond our control > unfortunately. > > Regarding your points, Steve: > > 1) If a company is stupid to "abandon" a

Re: http://www.groovy-lang.org/ down

Thanks for the explanation Guillaume. Just a quick question. I was wondering if, the same way Groovy has a mirror in Github, could it be possible to have the Groovy site published as a gh-pages? That would work as a possible documentation back-up in the future. Of course I don't mean to do it any

Re: http://www.groovy-lang.org/ down

And... it's back now! Sorry again for the inconvenience, but this was really beyond our control unfortunately. Regarding your points, Steve: 1) If a company is stupid to "abandon" a great language like Groovy, too bad for them ;-) 2) Well, we can't control perception obviously, and I didn't

Re: http://www.groovy-lang.org/ down

What about backing out the change for now? This is looking really bad...think about how it looks from the outside: 1) Pivotal appears to "abandon" Groovy as a language -- does not send a positive signal about the language's future prospects 2) _Without warning_ the groovy-lang.org