Last year’s move to the subscription model was motivated by our desire to release more often, focusing on continuous delivery of value independent of versioning. With that goal in mind, we started this year with RubyMine 2016.1, the first release in the series of releases planned for 2016. Now we’re glad to announce RubyMine 2016.2 EAP, a preview of the next IDE update planned for this summer!
Staying focused on polishing the key IDE features, in this release we continue to work on better code insight, new refactorings, smoother gem management experience, and other features you use every day. We also have a lot of new features coming from IntelliJ Platform and hope you will like them as well.
Please stay tuned as we’re going to publish posts about all the most interesting 2016.2 new features during the summer. As of today, let me share a couple of neat new features that help make RubyMine easier on your eyes.
Please welcome RubyMine 2016.1.1 (build 145.971). This update contains important fixes for two security issues inside IntelliJ Platform. The vulnerabilities, in various forms, are also present in older versions of the IDE; therefore, patches for those are also available. Please use “Check for Updates…” to download and install the update. Or, download RubyMine 2016.1.1 from our website.
We have had no reports of any active attacks against these vulnerabilities. However, it is strongly recommended for all users to install the update as soon as possible.
Please read more on the issues and ways to update in the company blog.
We have also fixed several issues on Ruby, Rails and HAML code parsing as well as some debugger issues. Please take a look at the release notes for more details.
Looking back at the history of Ruby and Rails, we can’t help but highlight 2006 – the year IntelliJ IDEA Ruby Plugin was released and the first RailsConf took place in Chicago. Now, ten years later, we’re excited that the RailsConf 2016 is about to begin.
The RubyMine team has visited RailsConf each and every year since 2010, and always got back from it inspired and full of new ideas for RubyMine, all thanks to the incredible Ruby community!
Nowadays, some say that Ruby and Rails are on the decline and the community is not as active as it used to be. Is this really true? Let’s find the answer together!
Take Part in a Ruby Community Survey
We want to ask you, Ruby developers all over the world: Do you agree that Ruby and Rails are not trendy any more? Please follow this page with three simple questions to help us find the answer. By answering, you also get a chance to win one of the Amazon certificates worth 75$ as we’re going to compliment the most interesting answers.
Meet Us at RailsConf 2016
You’re most welcome to join us at the JetBrains booth to discuss the topic, ask any questions on RubyMine, have a demo, or have a chat over a cup of coffee during the break! We will also be wearing our JetBrains Team T-shirts so you can easily find us around the show.
As of today we start the final countdown for RubyMine 2016.1 release. Please welcome RubyMine 2016.1 Release Candidate (build 145.596) that you can now download and try. If you have a previous Beta build (145.256) installed, you should soon get a notification in the IDE about a patch update.
Hi Marcin, Robert, thank you for taking the time to speak with us. I believe all Rails developers interested in React.js already know you, but for those who don’t, can you tell us a bit about yourselves?
Robert: Yo! A few years ago I was disappointed by Rails speed in development mode so I wrote the active_reload library. It was later incorporated in Rails 3.2 so everyone benefits from it every day. I blog regularly about Ruby, Rails and React.js and some of those posts have thousands of readers every month
We’re entering the homestretch and getting ready for the next major RubyMine 2016.1 release with Beta build 145.256, which you can learn more about and download from our website.
You are probably wondering why we’re using 2016.1 version number instead of 8.5. With the recent move to the subscription model, we planned to release more often and move away from the major/minor versioning scheme, focusing on continuously delivering value independent of versioning. In addition, we want to align the versioning and releases timetables of all products that comprise JetBrains Toolbox. So these are the two reasons for the versioning change from 8.5 to 2016.1. To find out more about this, please check this post in our company blog.
At any rate, this build is focused on the bug fixes and improvements in the recently added features. The full list of issues addressed in this build is available in the release notes.
We are looking forward to getting your feedback in our issue tracker. If you have the previous EAP build (145.184) installed, you should soon get a notification in the IDE about a patch update. To get notifications of new EAP builds as they become available, subscribe to the EAP channel in Preferences | Appearance & Behavior | System Settings | Updates.