What is the difference between the version and code of eclipse?

This is a very interesting question. Here are two good answers:

1. the version number of eclipse (x.y. z) is meaningful. X indicates that its API has a destructive update, y indicates that its API has no destructive update, and Z indicates that the bug is corrected. The projects here now have different versions, such as platform 3.2, tptp 4.2, Birt 2.1, CDT 3.1, and EMF 2.2. If we force each project to use a general version (3.2), some projects will return previous versions (tptp ), in other projects, this version (Birt and EMF) must be skipped if the API is not updated. We do not want to force the project to convert the name without compromising the meaning of the version, so we do not want to use a general version number.
 

2. Different eclipse projects have different release cycles. Some projects are released once a year (such as platform), some projects are released twice a year (such as tptp and Birt), and others are released multiple times a year. If you force a project to use a uniform version number, you must limit the speed of the project to be released and the progress of the project to be released. This seems incorrect.

Therefore, we kept the version numbers of each project independent and used a word-based solution (Jupiter's satellite) to generate a co-release version. This year is Callisto, and next year it will be Europa ).

What logic is Callisto, which is replaced by Mu Weisi next year?

The answer is the distance between Jupiter's satellites and Jupiter.

Callisto guard is one of the four brightest satellites of Jupiter, the sixth satellite from Jupiter.
Europa guard, one of the four brightest planets of Jupiter, is the seventh satellite of Jupiter.

Io (MU Wei 1), Europa (MU Wei 2), Ganymede (MU Wei 3), Callisto (MU Wei 4)