Community
Participate
Working Groups
There have been some platform ui changes but no API changes yet. Our bundle versions should be 3.7.100 then, not 3.8.0. PW
I think some (JFace?) already have API additions and there the version is fine.
You are correct, the workbench change did not need a minor version increase, my bad. At this point we could leave it at 3.8 or change it to 3.7.100. Considering that it has been 3.8 in two I-builds, I'd prefer to leave it at 3.8 - there is no real harm in that. I'll leave the decision to you. (Other changes: - the JFace got an API addition (see bug 203950). - some graduated e4 core bundles had < 1.0 version numbers. After consulting with John I updated version number to 1.0 on the bundles I modified in Head.)
(In reply to comment #2) > At this point we could leave it at 3.8 or change it to 3.7.100. Considering > that it has been 3.8 in two I-builds, I'd prefer to leave it at 3.8 - there is > no real harm in that. I'll leave the decision to you. Ideally we should be switching to 3.7.100, but considering that there will be API changes anyways, I'll vote for leaving it as 3.8. Please reopen if you oppose.
(In reply to comment #2) > You are correct, the workbench change did not need a minor version increase, my > bad. > > At this point we could leave it at 3.8 or change it to 3.7.100. Considering > that it has been 3.8 in two I-builds, I'd prefer to leave it at 3.8 - there is > no real harm in that. I'll leave the decision to you. I'm fine with it. Just keep it in mind for future bundle version changes.
There's one issue: org.eclipse.ui has new content but the version has not yet been increased.
(In reply to comment #5) > There's one issue: org.eclipse.ui has new content but the version has not yet > been increased. Updated bundle version to 3.7.100 in the R3_development branch. Paul has made the same change in R4_development branch in the bug 349255.
