@@ -42,7 +42,7 @@ For archiving purposes, the release is also published in a separate folder
4242for each version, with the archive in the top folder and the p2 repo as
4343a sub-folder
4444
45- - < https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905 .zip >
45+ - < https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712 .zip >
4646- < https://download.eclipse.org/embed-cdt/releases/6.6.0/p2/ >
4747
4848The official download page is
@@ -146,11 +146,11 @@ This will also trigger a GitHub Actions CI job that will run a maven build.
146146
147147Note: this happens now automatically, at each push.
148148
149- - go to [ https://ci.eclipse.org/embed-cdt/job/build-plug-ins/ ] ( https://ci.eclipse.org/embed-cdt/job/build-plug-ins/ )
149+ - go to < https://ci.eclipse.org/embed-cdt/job/build-plug-ins/ >
150150- ** login** (otherwise the next link is not visible!)
151151- click the ** Scan Multibranch Pipeline Now** link
152152- when ready, the p2 repository is published at
153- [ https://download.eclipse.org/embed-cdt/builds/develop/p2/ ] ( https://download.eclipse.org/embed-cdt/builds/develop/p2/ )
153+ < https://download.eclipse.org/embed-cdt/builds/develop/p2/ >
154154
155155### Install on a separate Eclipse
156156
@@ -169,11 +169,11 @@ Wait for the GitHub Actions CI job to confirm that the build passed.
169169
170170### Trigger the Jenkins master build
171171
172- - go to [ https://ci.eclipse.org/embed-cdt/job/build-plug-ins/ ] ( https://ci.eclipse.org/embed-cdt/job/build-plug-ins/ )
172+ - go to < https://ci.eclipse.org/embed-cdt/job/build-plug-ins/ >
173173- ** login** (otherwise the next link will not be visible!)
174174- click the ** Scan Multibranch Pipeline Now** link
175175- when ready, the p2 repository is published at
176- [ https://download.eclipse.org/embed-cdt/builds/master/p2/ ] ( https://download.eclipse.org/embed-cdt/builds/master/p2/ )
176+ < https://download.eclipse.org/embed-cdt/builds/master/p2/ >
177177
178178### Publish the release candidate
179179
@@ -195,7 +195,7 @@ Go to the release candidate folder
195195
196196- < https://download.eclipse.org/embed-cdt/release-candidates/ >
197197
198- Get the timestamp (like 202403210905 ) and update the README-MAINTENANCE.md file.
198+ Get the timestamp (like 202404031712 ) and update the README-MAINTENANCE.md file.
199199
200200Commit with _ README-MAINTAINER update timestamp_ .
201201
@@ -252,11 +252,11 @@ With a Git client:
252252- open ` simrel.build-fork.git `
253253- pull new commits
254254- edit ` embedcdt.aggrcon `
255- - replace location to < https://download.eclipse.org/embed-cdt/release-candidates/6.6.0-202403210905 /p2/ >
256- - replace full version to ` 6.6.0.202403210905 `
255+ - replace location to < https://download.eclipse.org/embed-cdt/release-candidates/6.6.0-202404031712 /p2/ >
256+ - replace full version to ` 6.6.0.202404031712 `
257257 - replace short version to ` 6.6.0 `
258258- commit with a message like:
259- - _ embedcdt: update for 6.6.0-202403210905 release candidate_ ,
259+ - _ embedcdt: update for 6.6.0-202404031712 release candidate_ ,
260260- push
261261- create pull request
262262
@@ -273,7 +273,7 @@ In about 7-8 minutes it'll automatically rebuild the staging repo:
273273
274274Announce the release candidate to the ** embed-cdt-dev@eclipse.org ** list;
275275use a subject like
276- ** Embed CDT v6.6.0-202403210905 release candidate** ,
276+ ** Embed CDT v6.6.0-202404031712 release candidate** ,
277277and pass a link to the release page, available at:
278278
279279- < https://projects.eclipse.org/projects/iot.embed-cdt/ >
@@ -286,9 +286,9 @@ Beta testers can install the release candidate from:
286286
287287Go to the release candidate folder
288288
289- - [ https://download.eclipse.org/embed-cdt/release-candidates/ ] ( https://download.eclipse.org/embed-cdt/release-candidates/ )
289+ - < https://download.eclipse.org/embed-cdt/release-candidates/ >
290290
291- Copy the tag and enter it in Git, like ` v6.6.0-202403210905 ` (with ` v ` ).
291+ Copy the tag and enter it in Git, like ` v6.6.0-202404031712 ` (with ` v ` ).
292292
293293## Publish the final release
294294
@@ -342,12 +342,12 @@ In the `develop` branch, in `_posts/plugins/releases`, add a new release page.
342342As links for the latest two, open < https://download.eclipse.org/embed-cdt/releases/ >
343343and get the archive URL, like:
344344
345- - < https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905 .zip >
345+ - < https://download.eclipse.org/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712 .zip >
346346
347347Isolate the part starting with ` /embed-cdt/... ` and update the URLs to use the download redirect:
348348
349- - < https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905 .zip >
350- - < https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202403210905 .zip.sha >
349+ - < https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712 .zip >
350+ - < https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.6.0/org.eclipse.embedcdt.repository-6.6.0-202404031712 .zip.sha >
351351
352352Go to < https://github.com/eclipse-embed-cdt/eclipse-plugins/milestones > and
353353update the fixed issues.
0 commit comments