CLion 2016.1 Release Candidate

Anastasia Kazakova

Hi everyone,

We are approaching the final steps towards the CLion 2016.1 release, so it would be a good time to explain where the 2016.1 version number has come from.

As you may know, this release was previously announced as 1.5. So you might ask, is this a major or minor upgrade?

In fact it’s kind of both, because it’s got enough important features to qualify as a major upgrade, but at the same time, it’s versioned as a minor upgrade. So what gives?

Well, with the move to a subscription model, we planned to release more often and move away from major/minor versioning scheme, focusing on continuously delivering value independently of versioning. This along with aligning versioning and releases of all the products under the JetBrains Toolbox, are the reasons for the versioning change from 1.5 to 2016.1.

To find out more about this, please check the post we’ve just published on our company blog.

From the C++ side this build addresses a few issues:

  • Incorrect code generation when using iter live template (CPP-5987).
  • False “local variable assigned but never accessed” warning when using Google Tests (CPP-1012).
  • Code analysis failure when std::string and const char[] are concatenated (CPP-4681).

Another change affects our Swift plugin. Now you don’t need to download a separate .jar file – install the plugin from our repository instead.

Find the full release notes by the link.

CLion 2016.1 Release Candidate (build 145.256) is out today and available for download. Or get a patch-update if you are using previous EAP build. (The patch-update is not available on Windows platform this time. We are sorry for the inconveniences.)

On the new Preview Next Version page on our site you can find the details about all the new features coming to CLion 2016.1. And if you find any bug at all, please file an issue in our tracker.

The CLion Team
The Drive to Develop

Comments below can no longer be edited.

24 Responses to CLion 2016.1 Release Candidate

  1. Даниил Водопьян says:

    March 10, 2016

    Previously a major release might mean that the IJ platform changed, the architecture shifted or something incompatible happened. So it was wise to postpone updating to 14.0 release and wait for 14.1 with all the bugfixes.

    What is the situation now? Can you give us a hint when the probability of bugs is greater than usual?

    • Anastasia Kazakova says:

      March 10, 2016

      Thanks for the interesting opinion about our previous versioning.
      Our goal now is to make all the releases both – stable and full-featured – to bring value to our customers. So hopefully we’ll be able to deliver proper stable solutions to you with every year.x release. For sure, if some problems are met there, there will be bug fix updates shortly.

  2. Alexander Münch says:

    March 10, 2016

    After updating to this new version a “CLion Privacy Policy Agreement” popup opened. What about that?

    I know the option to grant you anonymous statistics for plugin and feature usage. This I can control in settings. Why can’t I run the IDE now without accepting this new agreement?

    What has changed? What information do you need more since the last CLion build?

    Don’t get me wrong. In all my JetBrains products I opted in to let you know what features I use. But I want to know what information I am granting you insight. This new agreement worries me.

    • Anastasia Kazakova says:

      March 10, 2016

      The Privacy Policy displayed is the exact same one that has been available on our site The only difference is that in addition to providing this policy during the Purchase Process, we are now displaying in product too.

      We do not collect any anonymous usage statistics unless you permit us to do so and this is controlled directly via the product under Usage Statistics.

      In essence, there is no changes, other than it being displayed in product.

  3. Yury V. Zaytsev says:

    March 10, 2016

    So, did the `boost::optional` bugfix make it into this EAP? Judging from the release notes, it seems it didn’t. Hopefully gets this fixed before release though, optional types are like… all over the place :-/

    • Anastasia Kazakova says:

      March 10, 2016

      If you mean this ( it’s still in development. I’m afraid it won’t make it way to the release, but then we’ll put it into the bug fix updates coming shortly.

      • Yury V. Zaytsev says:

        March 10, 2016

        I see, thanks for the update!

  4. Yury V. Zaytsev says:

    March 10, 2016

    Any insights on how the EAPs are going to be versioned in the future? Is this just going to be the full build number, like YYYY.R.N.M?

    The new versioning scheme will take some time to get used to… :-/ Still, it does feel like an improvement over the old system.

    I wonder if you have seriously considered Ubuntu-style versions (14.04 / 16.04) and why this option was eventually discarded. It’s less redundant (I don’t see the “20” part of “2016” to change more often than ~ every 100 years) and thus shorter & easier to type. Most importantly for me, a leading zero properly aligns minor version numbers, such that the entire version strings can be alphabetically sorted, which means that everything is pleasant and easy: input field sizes, filenames ordering, etc. (cf. clion-2016.1.tar.gz / clion-2016.11.tar.gz / clion-2016.2.tar.gz)

    • Anastasia Kazakova says:

      March 11, 2016

      YES, EAP builds will have build numbers in the described format: YYYY.R.N.M.

      We considered the Ubuntu’s style for sure, but wanted to stress that the first part relates to the year not to confuse our current users with, for example, version 16)

      Since R is a consequent number of the release during the year, not sure if we really need a leading zero, since having >9 releases during the year looks not that realistic.

  5. Mehdi says:

    March 10, 2016

    I liked the previous versioning scheme more 🙁

    • Anastasia Kazakova says:

      March 11, 2016

      Thanks for pinging us. Unfortunately, looks like they are not making their way to the release, but we’ll consider them for further updates.

  6. Anton says:

    March 11, 2016

    Is there a chance that you’ll separate the highlighting of built-in types in near future (

    • Anastasia Kazakova says:

      March 11, 2016

      Yes, we’ll consider the original request ( for further releases, however first we need to resolve issues with higher prio. Feel free to upvote and follow to get updates.

  7. Olof says:

    March 11, 2016

    This is coming from the left field, but are there any plans to provide pretty printing for gcc compiler errors in the messages window? They are excruciatingly hard to read, often with 20+ lines for one error.

    And with a compiler error in template heavy code I just push it to the integration server and leave for the day.

    Well, that last one was a joke.

  8. Anton says:

    March 12, 2016

    Debugger variable redisplay is horribly slow and from my point of view, this issue must have a top priority (I can’t use CLion for debugging at all). Do you plan to finally improve the situation?

    • Anton Makeev says:

      March 12, 2016

      We sincerely apologize for this issue. We are working on it at this moment and hope to publish the fix with one of 2016.1 updates.

  9. Roman says:

    March 13, 2016

    IDE hanged 3 times during the day. Never experienced that before with previous Clion versions.

    • Anastasia Kazakova says:

      March 13, 2016

      Could you please share more details to our support ( We would really appreciate your help and will try to help/improve.

      • Roman says:

        March 13, 2016

        I’ve invalidated caches, now have about 3 hours of uninterrupted coding. If it hangs again I’ll send logs.

        • Anastasia Kazakova says:

          March 14, 2016

          Thanks. And sorry for the inconvenience.


Subscribe for updates