|
|
|
|
| Re: Community support on Eclipse versions [message #1734249 is a reply to message #1734053] |
Mon, 06 June 2016 14:30  |
 Eric Rizzo
Messages: 3070
Registered: July 2009 |
Senior Member |
|
|
Arturo Pena wrote on Fri, 03 June 2016 11:29So what gets fixed then? The latest release only? The last two? How do I find out? Also, how do I report problems w/ a supported version?
Thanks.
Generally (and unofficially) speaking, only the current release branch and the next major release branches are going to get bug fixes. Each project is managed independently, so there can be some variation in that policy and in when releases come. But for most users of Eclipse IDEs, they're mostly concerned with the annual release trains (Eclipse does a major package release every year in June, each with a "friendly" code name). There are also 2 minor updates for each annual release (sometimes called Service Releases (SR1 and SR2).
For example, in June 2016 the Mars release came out, followed by Mars SR1 in September 2015 and Mars SR2 in February 2016. The next major release, in June 2016 will be Neon, with Neon SR1 and SR2 to follow. Basically, before Neon is released, bugs will only be fixed in the Mars SR1 or SR2 releases, and/or in the Neon release. The version previous to Mars, called Luna, did not receive bug fixes after Luna SR2. Similarly, Mars will no longer receive bug fixes since Mars SR2 is already released and Neon is almost at release point.
Once Neon is released, bug fixes will be done for Neon SR1 and SR2, as well as the next major release (code-named Oxygen).
So to put it another way, only the current release and the next release (usually) get bug fixes. If you need something older fixed, do it yourself or go to the LTS site that Ed mentioned.
|
|
|
Powered by
FUDForum. Page generated in 0.08352 seconds
] 
Search
Help
Register
Login
Home
