@@ -42,7 +42,7 @@ For archiving purposes, the release is also published in a separate folder
42
42
for each version, with the archive in the top folder and the p2 repo as
43
43
a sub-folder
44
44
45
- - < https://download.eclipse.org/embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202206121057 .zip >
45
+ - < https://download.eclipse.org/embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202208180721 .zip >
46
46
- < https://download.eclipse.org/embed-cdt/releases/6.3.0/p2/ >
47
47
48
48
The official download page is
@@ -192,6 +192,8 @@ Go to the release candidate folder
192
192
193
193
Get the timestamp and update the README-MAINTENANCE.md file.
194
194
195
+ Commit with _ README-MAINTAINER update timestamp_ .
196
+
195
197
### Create a release candidate record
196
198
197
199
This applies only for the first release candidate, or for the final release.
@@ -248,14 +250,14 @@ In Eclipse:
248
250
- right click: ** Show Properties View**
249
251
- in the right side, edit the ** Location** field to the new release
250
252
candidate p2 URL (like
251
- ` https://download.eclipse.org/embed-cdt/release-candidates/6.3.0-202206121057 /p2/ `
253
+ ` https://download.eclipse.org/embed-cdt/release-candidates/6.3.0-202208180721 /p2/ `
252
254
and press Enter
253
255
- select all the features in the contribution, right-click and choose
254
256
** Fix Versions**
255
257
- select the Contribution and ** Validate**
256
258
- select the Aggregation and ** Validate**
257
259
- Save
258
- - commit _ embedcdt: update for 6.3.0-202206121057 '_
260
+ - commit _ embedcdt: update for 6.3.0-202208180721 '_
259
261
- _ Signed-off-by: Liviu Ionescu
< [email protected] > _
260
262
- _ Signed-off-by: Liviu Ionescu
< ; [email protected] > ; _
261
263
@@ -284,7 +286,7 @@ In about one hour it'll automatically rebuild the staging repo:
284
286
285
287
Announce the release candidate to the
** [email protected] ** list;
286
288
use a subject like
287
- ** Embed CDT v6.3.0-202206121057 release candidate** ,
289
+ ** Embed CDT v6.3.0-202208180721 release candidate** ,
288
290
and pass a link to the release page, available at:
289
291
290
292
- < https://projects.eclipse.org/projects/iot.embed-cdt/ >
@@ -299,7 +301,7 @@ Go to the release candidate folder
299
301
300
302
- [ https://download.eclipse.org/embed-cdt/release-candidates/ ] ( https://download.eclipse.org/embed-cdt/release-candidates/ )
301
303
302
- Copy the tag and enter it in Git, like ` v6.3.0-202206121057 ` (with ` v ` ).
304
+ Copy the tag and enter it in Git, like ` v6.3.0-202208180721 ` (with ` v ` ).
303
305
304
306
## Publish the final release
305
307
@@ -352,12 +354,12 @@ In the `develop` branch, in `_posts/release`, add a new release page.
352
354
As links for the latest two, open < https://download.eclipse.org/embed-cdt/releases/ >
353
355
and get the archive URL, like:
354
356
355
- - < https://download.eclipse.org/embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202206121057 .zip >
357
+ - < https://download.eclipse.org/embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202208180721 .zip >
356
358
357
359
Isolate the part starting with ` /embed-cdt/... ` and update the URLs to use the download redirect:
358
360
359
- - < https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202206121057 .zip >
360
- - < https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202206121057 .zip.sha >
361
+ - < https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202208180721 .zip >
362
+ - < https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.3.0/org.eclipse.embedcdt.repository-6.3.0-202208180721 .zip.sha >
361
363
362
364
Update the milestone URL.
363
365
0 commit comments