How to automatically keep up-to-date with the latest M*/RC* and GA releases? #2920
-
|
Hi all, Is there a way I can get the latest M*/RC*/GA releases for my installation as soon as they are available? The idea is to have our developers update our IDEs as frequently as possible without having to manually change anything (or changing as little as possible) in the Oomph setup. For reference, we have 2 kinds of IDEs, which we deliver using Oomph:
What I do is:
What I plan to do is:
Questions
Thank you in advance for your help and sorry for the lengthy questions. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
|
@fedejeanne just add this update site to your eclipse https://download.eclipse.org/releases/milestone/ (I'm already using that since a while and it works like a charm). It would be good to have this mentioned somewhere on the download page like:
|
Beta Was this translation helpful? Give feedback.
-
|
I plan to show users a page like this one where we ask the user if they want to update to Java 24 support: eclipse-oomph/oomph#134 (comment) When M1 is available, we can ask the user if they want to install early access features immediately to get new features immediately and to help test that. Note only that, we don't have to tell them what to do we can literally do it for them... |
Beta Was this translation helpful? Give feedback.
-
+1 . Who takes care of the download page?
I like the idea, it would help gather more testers! I assume this means that one has to run perform setup tasks at least once with the check enabled, right? |
Beta Was this translation helpful? Give feedback.
-
|
No, that's a different thing specific to the Platform. The Eclipse project catalog is updated the day of the actual release but because master is opened before the release is actually finished and also before the Platform's release p2 update site is actually at a final permanent location I update the following tasks to do redirection conditionally and then after the release I disable them again, prepping them for the next cycle: For issues about the website one can open them here: https://gitlab.eclipse.org/eclipsefdn/it/websites/eclipse.org/-/issues/755 I suggest going though the IDE WG for anything one might want to change on these pages... Keep in mind that people do not read because they're too busy and too goal oriented. They also cannot follow instructions for the same reason. Moreover many people do not get to the download page at all because they download the installer from here: https://www.eclipse.org/downloads/ And finally many people do not download at all because they simply update. So while suggesting instructions for doing something helping might have some impact, I expect it will be missed, ignored, or overlooked by a vast majority of the users. A view opened in the IDE is harder to overlook and with buttons that do the necessary steps, it's harder to do it incorrectly. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, ok. I re-read your comment @merks and now I interpret that you want to provide a new page like the one you posted (about using Java 24) so there is no need to add anything into the website. Is that correct? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I don't think we really need it on the website if we will be telling people about it explicitly from within their IDE, which I plan to do... |
Beta Was this translation helpful? Give feedback.
-
|
This will always point at the latest release: I.e., currently This will always point at the not-yet-released visible milestone I.e., currently But, because we have not yet done 2025-06 M1, it just composes these at the moment: I.e., it's kind of a fake next release repository until M1 at which point it will compose the actual 2025-06 milestone Another set of URLs that's really bleeding edge, are staging repositories:
There is no staging latest; no one has asked and I generate the Oomph product catalogs so the generator doesn't need that. These sites are actually a bit "dangerous" because the content is overwritten arbitrarily at any time... I don't know the catalog structure of your tasks. In the Eclipse projects catalog I maintain these variables that could be used.
I'm not sure it's really necessary to have such exact strict bounds on the rcp feature... |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the detailed explanation, @merks ! I'm going to try @laeubi's suggestion with the milestone URL and remove the versions on the RCP feature like I planned (and you also suggested) :-) |
Beta Was this translation helpful? Give feedback.
-
@merks https://download.eclipse.org/releases/milestone/ still points 2025-03. Do you know when it will be updated to point to 2025-06 M1? |
Beta Was this translation helpful? Give feedback.
-
|
From here: You can always find the link for the current release's schedule, currently th is: Where you can see M1 is this coming Friday. |
Beta Was this translation helpful? Give feedback.
@fedejeanne just add this update site to your eclipse https://download.eclipse.org/releases/milestone/ (I'm already using that since a while and it works like a charm).
It would be good to have this mentioned somewhere on the download page like: