Homebrew requires a version, checksum and the download-link, which
contains a placeholder for the 2nd part of the version number (the
correct 2023-09).
So when the binaries do not change, the confusing version number can be
fixed there now and it is the only change, that need to be done there.
All the update sites are sound and have the correct content.
The only problem is that this link does not exist because someone
overlooked creating it:
https://projects.eclipse.org/projects/eclipse/releases/4.29.0
As a result, this mostly-generated page cannot point to it:
Hi Ed,
does this mean only the organisational things and the site needs a fix
or does this mean a patch release (i.e. 4.29.1 with updated release
notes etc.) is required to fix this?
So does this need to be fixed before the Homebrew issue can be fixed
(the existing version only references an
It looks like the Eclipse project forgot to create a release record for
4.29:
https://projects.eclipse.org/projects/eclipse/governance
I did ask folks to review their release records, and to create new ones
where appropriate, well ahead of when Wayne created the PMI page on this
issue:
Great news!
But I wonder about the deviation of the contained project version
numbers included in Eclipse 2023-09
(https://projects.eclipse.org/releases/2023-09):
- Eclipse Project 4.28.0
(https://projects.eclipse.org/projects/eclipse/releases/4.28.0)
- Eclipse Packaging 4.29.0
