Eclipse Community Forums: Java Development Tools (JDT)

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Understanding versioning(IDE Versioning)

Show: Today's Messages :: Show Polls :: Message Navigator

Understanding versioning [message #1827833]

Mon, 25 May 2020 09:18

Jeff Mutonho

Messages: 3
Registered: May 2020

Junior Member

According to the official Eclipse documentation, the current
verion (released in March 2020) is 4.15. The upcoming one, 4.16 wii
be out in June.
Does that mean any fixes, be it security or bugs, will not be back-ported to
4.15? How does the Eclipse IDE release philosophy work?
Thank you.

Report message to a moderator

Re: Understanding versioning [message #1827847 is a reply to message #1827833]

Mon, 25 May 2020 14:04

Ed Merks

Messages: 31543
Registered: July 2009

Senior Member

Yes there is a new release every quarter as part of the "Simultaneous Release"

https://wiki.eclipse.org/Category:SimRel-2020-06

All bug fixes (all changes) are done on "master" and master leads to the next release. For JDT there is typically a beta branch for work towards the next Java release, i.e., Java 15 will be the next one. That gets merged into master after the Java release.

So no, there are no maintenance streams generally supported although some people fork such things and do such work.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Understanding versioning [message #1827854 is a reply to message #1827847]

Mon, 25 May 2020 17:12

Ed Willink

Messages: 6874
Registered: July 2009

Senior Member

HI

The problem hasn't really arisen yet.

If a really bad problem occurs in the couple of days before release, 4.16 would be respun and still be 4.16.

A couple of days later and it might be 4.16a.

A couple of weeks later and it might be 4.16.1

But given that the worst problems are generally discovered before release and that many problems take some to-ing and fro-ing to agree on a repro, a diagnosis, a fix, a severity and testing, 4.17 three months later may not be that dreadfully late.

Occasionally individual projects may back port a particularly embarrassing fix. OCL backported a 6.11.0 fix to 6.10.1 after 9 weeks.

Regards

Ed Willink

Report message to a moderator

Re: Understanding versioning [message #1831589 is a reply to message #1827854]

Mon, 24 August 2020 11:12

Jeff Mutonho

Messages: 3
Registered: May 2020

Junior Member

Thank you very much for your responses. So from a planning point of view, could I assume that if I'm on 2020-06 (Current release) 4.16-June 17, 2020, when the (Upcoming release) 4.17 September 16, 2020 is released,
and I upgrade to that (i.e. 4.17), all features that were in 4.16 will now be incorporated into 4.17 (with fixes and enhancements? Ideally, that would mean one can dump the 4.16 knowing that 4.17 supersedes all features from 4.16 plus more, correct?
Thank you for responses.

Report message to a moderator