Community
Participate
Working Groups
I noticed that the a Feature in SR1 had a version number less than that of SR0. In SR1 the version was 3.0.0.R30x.... whereas in SR0 it was 3.0.0.v201005.... Because qualifiers are compared using strings, the 'v' comes after the 'R'. While I brought this to the attention of the team in question, I think this raises a bigger concern. We put a lot of faith in our version numbers, and it's very easy to get these wrong. API tools help, but they won't necessarily catch bundles / features that are going backwards in time (especially if you don't update your baseline). I think we need two things here: 1. Some general education about versions and the consequences of getting these wrong. -- I assume once you've 'released' something with a version, you should *never* go back. 2. Some tooling in the release train to help catch backward versioning.
+1 I think especially the tooling in the release train would be very helpful. Currently, only a few participating projects run API tooling during their build. IMHO it should be mandatory for participating projects.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/137.
