RIP PhantomJS

Due to the lack of active contribution, I am going to archive this project soon.
At some point in the future, if we pick up the development again (such as #15341, #15342, #15343), the project will be unarchived.
With that, all the earlier plans regarding PhantomJS 2.5 (from @Vitallium) or 2.1.x (from @pixiuPL) will be abandoned effective immediately. Consequently, the source and binary packages for the above abandoned version will be removed to avoid any confusions. PhantomJS version 2.1.1 will remain the last known stable release until further notice.
To keep the source repository in a sane situation:
the master branch will be preserved under the new bleeding-edge branch.
after that, the master branch will be restored back to the approximate state of v2.1.1
That way, if anyone wants to improve PhantomJS for their own usages (internal fork, in-house patches), the master branch can still serve as a good baseline. It can still be built from


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/ja6gWd7cziw/15344

Original article

Slashdot Outage Update

Obviously Slashdot has had some issues the past couple days. For those wondering, we inherited an aging hardware setup in the acquisition that was located physically far away from us. We made a big investment in a new hardware set up, and ran into sizable issues including a massive DDOS during the migration process. Going forward we expect much better uptime. If we inconvenienced anyone, we’re sorry. If it’s any consolation, it wasn’t fun for us either, and our team worked non-stop for days to get Slashdot back online. With our new infrastructure in place, we will be dedicating a lot of time and resources this year to improving Slashdot.

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/JyuKTmWNYak/slashdot-outage-update

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: