PhpStorm 2016.1 RC1 is available along with new versioning

We are glad to announce that PhpStorm 2016.1 RC1 build 145.256 is available for download. If you want to learn all the details about the new features or to get yourself a copy to try right away, please visit our website.

Please see our issue tracker for the full list of PHP-related issues fixed and release notes.


In this build you will also notice that directory where IDE settings are stored was changed. Directory name was changed form WebIde to  PhpStorm2016.1,  during the first run you will be automatically suggested to migrate your settings to the new location.

For more information please look at the overview of all PhpStorm 2016.1 features and download the build from PhpStorm website. A patch update is already available from the previous EAP build (PhpStorm 11 EAP 145.184).

If you have any feedback to share with us, please do so in the forum, comments to this blog post, or the issue tracker, as the PhpStorm 2016.1 release is just around the corner!

Versioning Changes

Yesterday we introduced a new versioning scheme for all the products under the JetBrains Toolbox  which will follow the format


where yyyy represents the year, and r the release within that year.  New versioning is the next step in making process more transparent while having multiple releases per year. Read more about versioning changes in this blog post.

The Drive to Develop!
-JetBrains PhpStorm Team

This entry was posted in Early Access Program, Release Announcements and tagged , . Bookmark the permalink.
  • ConstB

    sorry, but YYYY is too much noise, YY would be enough really.

    • Renato Mendes Figueiredo

      YY.R would almost look like its right now, since they are releasing like crazy to invalid old licenses they would get to version 16 in a few months! haha

    • Chris Deeming

      Is noise really that much of a consideration with regards to product versioning? You could always abbreviate it, if wished, to ‘16.1. Come to think of it, assuming that there’s no longer a third point, you could say the new versioning is the same length: 10.0.3 vs 2016.1

      EDIT: I actually just read the blog post — there will be some lengthier versions of the version number for different builds within the same release. Still, doesn’t bother me. It’s just a version number.

    • butlerpcnet

      But that would lead to confusion in the year 2100…

      • ConstB

        yeah, right. you know, let our grandchildren worry about that…

  • Nicolas Bailly

    Could the issue with non QWERTY keyboard in the terminal (, ) be fixed before release please ?

    It’s quite important for me as I use the integrated terminal a lot.


  • Piotr Rybałtowski

    I’m glad you’ve changed it. Difference between 9.0, 10.0 and 11.0 were so small it was more confusing than helping actually.