Consider a Java/Eclipse update policy

From https://www.eclipse.org/lists/escet-dev/msg00303.html:

[...] why do we move to the next eclipse and java version if available every single time? (although java isn't changed this time iirc). It causes a lot of work both for release and for installing/updating, and it's not like entire Eclipse or Java is completely obsolete in 3 months. Running the newest release is useful for development, but for production use it's just horrible. Industry will likely just stick to an older version instead rather than risking updating trouble at a crucial point in their development cycle.

Let's discuss whether we can come to a sort of update policy for Java, Eclipse, etc. When do we update? How often?