Archiving the challenge: suspending the come · Disaster #15344 · ariya/phantomjs

Attributable to the lack of active contribution, I’m going to archive this challenge soon.

At some level in due route, if we enjoy up the come over again (such as #15341, #15342, #15343), the challenge will be unarchived.

With that, the total earlier plans referring to PhantomJS 2.5 (from @Vitallium) or 2.1.x (from @pixiuPL) will be deserted efficient straight away. This capacity that, the source and binary purposes for the above deserted version will be eliminated to lead clear of any confusions. PhantomJS version 2.1.1 will remain the final identified salvage liberate till additional detect.

To defend the source repository in a sane field:

• the master division will be preserved below the brand new bleeding-edge division.
• after that, the master division will be restored relief to the approximate utter of v2.1.1

That formulation, if anyone desires to present a enhance to PhantomJS for their grasp usages (inner fork, in-house patches), the master division can silent abet as a acceptable baseline. It will silent be built from source and this could silent work on macOS, Linux, and Dwelling windows.

As soon as the challenge is archived, no new field could be filed. Alternatively, in reality feel free to make use of the mailing-checklist to submit questions and focus on any connected issues.

Thank you for your figuring out!