Skip to content

Commit

Permalink
README update
Browse files Browse the repository at this point in the history
  • Loading branch information
ilg-ul committed Apr 3, 2024
1 parent 34ae4eb commit b5ff02b
Showing 1 changed file with 15 additions and 15 deletions.
30 changes: 15 additions & 15 deletions README-MAINTAINER.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

- <https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905.zip>
- <https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712.zip>
- <https://download.eclipse.org/embed-cdt/releases/6.6.0/p2/>

The official download page is
Expand Down Expand Up @@ -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 <https://ci.eclipse.org/embed-cdt/job/build-plug-ins/>
- **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/)
<https://download.eclipse.org/embed-cdt/builds/develop/p2/>

### Install on a separate Eclipse

Expand All @@ -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 <https://ci.eclipse.org/embed-cdt/job/build-plug-ins/>
- **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/)
<https://download.eclipse.org/embed-cdt/builds/master/p2/>

### Publish the release candidate

Expand All @@ -195,7 +195,7 @@ Go to the release candidate folder

- <https://download.eclipse.org/embed-cdt/release-candidates/>

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_.

Expand Down Expand Up @@ -252,11 +252,11 @@ With a Git client:
- open `simrel.build-fork.git`
- pull new commits
- edit `embedcdt.aggrcon`
- replace location to <https://download.eclipse.org/embed-cdt/release-candidates/6.6.0-202403210905/p2/>
- replace full version to `6.6.0.202403210905`
- replace location to <https://download.eclipse.org/embed-cdt/release-candidates/6.6.0-202404031712/p2/>
- 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

Expand All @@ -273,7 +273,7 @@ In about 7-8 minutes it'll automatically rebuild the staging repo:

Announce the release candidate to the **[email protected]** 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:

- <https://projects.eclipse.org/projects/iot.embed-cdt/>
Expand All @@ -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/)
- <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

Expand Down Expand Up @@ -342,12 +342,12 @@ In the `develop` branch, in `_posts/plugins/releases`, add a new release page.
As links for the latest two, open <https://download.eclipse.org/embed-cdt/releases/>
and get the archive URL, like:

- <https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905.zip>
- <https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712.zip>

Isolate the part starting with `/embed-cdt/...` and update the URLs to use the download redirect:

- <https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905.zip>
- <https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905.zip.sha>
- <https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712.zip>
- <https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712.zip.sha>

Go to <https://github.com/eclipse-embed-cdt/eclipse-plugins/milestones> and
update the fixed issues.
Expand Down

0 comments on commit b5ff02b

Please sign in to comment.