From b5ff02b586a936a0104daa760b2fde544ba7a3e9 Mon Sep 17 00:00:00 2001 From: Liviu Ionescu Date: Wed, 3 Apr 2024 20:22:43 +0300 Subject: [PATCH] README update --- README-MAINTAINER.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/README-MAINTAINER.md b/README-MAINTAINER.md index 34283f5a6..28e8e3794 100644 --- a/README-MAINTAINER.md +++ b/README-MAINTAINER.md @@ -42,7 +42,7 @@ For archiving purposes, the release is also published in a separate folder for each version, with the archive in the top folder and the p2 repo as a sub-folder -- +- - The official download page is @@ -146,11 +146,11 @@ This will also trigger a GitHub Actions CI job that will run a maven build. Note: this happens now automatically, at each push. -- go to [https://ci.eclipse.org/embed-cdt/job/build-plug-ins/](https://ci.eclipse.org/embed-cdt/job/build-plug-ins/) +- go to - **login** (otherwise the next link is not visible!) - click the **Scan Multibranch Pipeline Now** link - when ready, the p2 repository is published at -[https://download.eclipse.org/embed-cdt/builds/develop/p2/](https://download.eclipse.org/embed-cdt/builds/develop/p2/) + ### Install on a separate Eclipse @@ -169,11 +169,11 @@ Wait for the GitHub Actions CI job to confirm that the build passed. ### Trigger the Jenkins master build -- go to [https://ci.eclipse.org/embed-cdt/job/build-plug-ins/](https://ci.eclipse.org/embed-cdt/job/build-plug-ins/) +- go to - **login** (otherwise the next link will not be visible!) - click the **Scan Multibranch Pipeline Now** link - when ready, the p2 repository is published at -[https://download.eclipse.org/embed-cdt/builds/master/p2/](https://download.eclipse.org/embed-cdt/builds/master/p2/) + ### Publish the release candidate @@ -195,7 +195,7 @@ Go to the release candidate folder - -Get the timestamp (like 202403210905) and update the README-MAINTENANCE.md file. +Get the timestamp (like 202404031712) and update the README-MAINTENANCE.md file. Commit with _README-MAINTAINER update timestamp_. @@ -252,11 +252,11 @@ With a Git client: - open `simrel.build-fork.git` - pull new commits - edit `embedcdt.aggrcon` - - replace location to - - replace full version to `6.6.0.202403210905` + - replace location to + - replace full version to `6.6.0.202404031712` - replace short version to `6.6.0` - commit with a message like: - - _embedcdt: update for 6.6.0-202403210905 release candidate_, + - _embedcdt: update for 6.6.0-202404031712 release candidate_, - push - create pull request @@ -273,7 +273,7 @@ In about 7-8 minutes it'll automatically rebuild the staging repo: Announce the release candidate to the **embed-cdt-dev@eclipse.org** list; use a subject like -**Embed CDT v6.6.0-202403210905 release candidate**, +**Embed CDT v6.6.0-202404031712 release candidate**, and pass a link to the release page, available at: - @@ -286,9 +286,9 @@ Beta testers can install the release candidate from: Go to the release candidate folder -- [https://download.eclipse.org/embed-cdt/release-candidates/](https://download.eclipse.org/embed-cdt/release-candidates/) +- -Copy the tag and enter it in Git, like `v6.6.0-202403210905` (with `v`). +Copy the tag and enter it in Git, like `v6.6.0-202404031712` (with `v`). ## Publish the final release @@ -342,12 +342,12 @@ In the `develop` branch, in `_posts/plugins/releases`, add a new release page. As links for the latest two, open and get the archive URL, like: -- +- Isolate the part starting with `/embed-cdt/...` and update the URLs to use the download redirect: -- -- +- +- Go to and update the fixed issues.