update versions for 6.4.0

Author: ilg-ul

README-MAINTAINER.md

@@ -42,8 +42,8 @@ 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.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip>
-- <https://download.eclipse.org/embed-cdt/releases/6.3.2/p2/>
+- <https://download.eclipse.org/embed-cdt/releases/6.4.0/org.eclipse.embedcdt.repository-6.4.0-202304281106.zip>
+- <https://download.eclipse.org/embed-cdt/releases/6.4.0/p2/>
 
 The official download page is
 
@@ -92,7 +92,7 @@ page, click the
 [Milestones](https://github.com/eclipse-embed-cdt/eclipse-plugins/milestones/)
 button and add a
 [new](https://github.com/eclipse-embed-cdt/eclipse-plugins/milestones/new/)
-milestone. As title, use the current version, like _v6.3.2_.
+milestone. As title, use the current version, like _v6.4.0_.
 
 ### Update version in README-MAINTENANCE
 
@@ -121,17 +121,17 @@ For the plug-ins that were modified, increase the specific version
 
 Commit the MANIFEST.MF files as _update versions..._
 
-For all features, increase the common version (like _6.3.2_); be sure
+For all features, increase the common version (like _6.4.0_); be sure
 the composite records are not updated at this moment, they require
 new lines, added later.
 
 For all branding, edit the MANIFEST.MF and increase the
-`Bundle-Version` (like _6.3.2_).
+`Bundle-Version` (like _6.4.0_).
 
 For all other occurrences, except `compositeArtifacts.xml` and
 `compositeContent.xml`.
 
-Commit all with _update package version 6.3.2_.
+Commit all with _update package version 6.4.0_.
 
 ## Build locally
 
@@ -220,7 +220,7 @@ page, login and click the
 [Create a new release](https://projects.eclipse.org/node/18638/create-release/)
 link in the right side bar, below Releases (it shows only after login).
 
-Name it like `6.3.2` (no v).
+Name it like `6.4.0` (no v).
 
 Click the **Create and edit** button.
 
@@ -229,7 +229,7 @@ Click the **Edit** tab, **The Basics**; switch to Source mode
 Start with _Release candidate_ (Header 3).
 
 ```html
-<p>Version <strong>6.3.2</strong> is a maintenance release; it ....</p>
+<p>Version <strong>6.4.0</strong> is a maintenance release; it ....</p>
 
 <h3>Release candidate</h3>
 
@@ -270,7 +270,7 @@ In Eclipse:
 - right click: **Show Properties View**
 - in the right side, edit the **Location** field to the new release
 candidate p2 URL (like
-`https://download.eclipse.org/embed-cdt/release-candidates/6.3.2-202304281106/p2/`
+`https://download.eclipse.org/embed-cdt/release-candidates/6.4.0-202304281106/p2/`
 and press Enter
 - select all the features in the contribution, right-click and choose
 **Fix Versions**
@@ -279,7 +279,7 @@ and press Enter
 - Save
 - stage `simrel.aggr` & `embedcdt.aggrcon`
 - commit with a message like:
-  - _embedcdt: update for 6.3.2-202304281106_,
+  - _embedcdt: update for 6.4.0-202304281106_,
   - _Signed-off-by: Liviu Ionescu <ilg@livius.net>_
 - click the **Commit** button (do not Push yet)
 - right click, Show in local Terminal
@@ -309,7 +309,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.3.2-202304281106 release candidate**,
+**Embed CDT v6.4.0-202304281106 release candidate**,
 and pass a link to the release page, available at:
 
 - <https://projects.eclipse.org/projects/iot.embed-cdt/>
@@ -324,7 +324,7 @@ 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.3.2-202304281106` (with `v`).
+Copy the tag and enter it in Git, like `v6.4.0-202304281106` (with `v`).
 
 ## Publish the final release
 
@@ -333,9 +333,9 @@ When the plug-ins are considered stable:
 - in `eclipse-plugins.git`, the master branch, edit both .xml files
   - `repositories/org.eclipse.embededcdt-repository/composite/compositeArtifacts.xml`
   - `repositories/org.eclipse.embededcdt-repository/composite/compositeContent.xml`
-  - add new child like `<child location='../../releases/6.3.2/p2'/>`
+  - add new child like `<child location='../../releases/6.4.0/p2'/>`
   - update `p2.timestamp` to the value shown at the end of the `make-release-candidate-from-master`
-- **commit** master with a message like _add 6.3.2 to composite_
+- **commit** master with a message like _add 6.4.0 to composite_
 - **push** master
 
 - go to <https://ci.eclipse.org/embed-cdt/>
@@ -358,7 +358,7 @@ Both can be used in Eclipse to **Install New Software**.
 The public update URLs are:
 
 - <https://download.eclipse.org/embed-cdt/updates/v6/>
-- <https://download.eclipse.org/embed-cdt/releases/6.3.2/p2/>
+- <https://download.eclipse.org/embed-cdt/releases/6.4.0/p2/>
 
 ### Update the Eclipse Marketplace records
 
@@ -378,20 +378,20 @@ 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.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip>
+- <https://download.eclipse.org/embed-cdt/releases/6.4.0/org.eclipse.embedcdt.repository-6.4.0-202304281106.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.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip>
-- <https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.3.2/org.eclipse.embedcdt.repository-6.3.2-202304281106.zip.sha>
+- <https://www.eclipse.org/downloads/download.php?file=/embed-cdt/releases/6.4.0/org.eclipse.embedcdt.repository-6.4.0-202304281106.zip>
+- <https://www.eclipse.org/downloads/download.php?file=//embed-cdt/releases/6.4.0/org.eclipse.embedcdt.repository-6.4.0-202304281106.zip.sha>
 
 Update the milestone URL.
 
 Copy/paste the features/plug-ins from the console output of the
 [make-release-from-master](https://ci.eclipse.org/embed-cdt/job/make-release-from-master/)
 Jenkins job.
 
-- commit with a message like _Eclipse Embedded CDT plug-ins v6.3.2 released_.
+- commit with a message like _Eclipse Embedded CDT plug-ins v6.4.0 released_.
 - push the `develop` branch
 - wait for GitHub Actions job to complete
   (<https://github.com/eclipse-embed-cdt/web-jekyll/actions>)
@@ -405,18 +405,18 @@ Jenkins job.
 
 In [GitHub releases](https://github.com/eclipse-embed-cdt/eclipse-plugins/releases) add a new release
 
-- tag: _v6.3.2_ (with `v`)
-- title _Eclipse Embedded CDT plug-ins v6.3.2_
+- tag: _v6.4.0_ (with `v`)
+- title _Eclipse Embedded CDT plug-ins v6.4.0_
 - copy/paste from the release page
-- add `[Continue reading »](https://eclipse-embed-cdt.github.io/blog/YYYY/MM/DD/plugins-v6.3.2-released/)` with a link to the web page
+- add `[Continue reading »](https://eclipse-embed-cdt.github.io/blog/YYYY/MM/DD/plugins-v6.4.0-released/)` with a link to the web page
 - do not attach files
 - click **Publish release**
 
 ### Close milestone
 
 In [GitHub milestones](https://github.com/eclipse-embed-cdt/eclipse-plugins/milestones):
 
-- close the v6.3.2 milestone
+- close the v6.4.0 milestone
 
 ### Update the Eclipse release record
 
@@ -427,13 +427,13 @@ and select the new release
 - replace the entire content with links to GitHub:
 
 ```html
-<p>Version <strong>6.3.2</strong> is a new major/minor/service release; it updates ...</p>
+<p>Version <strong>6.4.0</strong> is a new major/minor/service release; it updates ...</p>
 
 <p>Fore more details, please read the project web release pages:</p>
 
 <ul>
  <li><a href="https://eclipse-embed-cdt.github.io/blog/YYYY/MM/DD/package-2020-12-released/">Eclipse IDE for Embedded C/C++ Developers 2020-12 released</a>&nbsp;(for installing a new Eclipse)</li>
- <li><a href="https://eclipse-embed-cdt.github.io/blog/YYYY/MM/DD/plugins-v6.3.2-released/">Eclipse Embedded CDT plug-ins v6.3.2 released</a>&nbsp;(for updating the plug-ins on an existing Eclipse)</li>
+ <li><a href="https://eclipse-embed-cdt.github.io/blog/YYYY/MM/DD/plugins-v6.4.0-released/">Eclipse Embedded CDT plug-ins v6.4.0 released</a>&nbsp;(for updating the plug-ins on an existing Eclipse)</li>
 </ul>
 ```
 
@@ -461,15 +461,15 @@ In Eclipse:
 - select **Mapped Repository**
 - right click: **Show Properties View**
 - in the right side, edit the **Location** field to the new release p2 URL
-(like `https://download.eclipse.org/embed-cdt/releases/6.3.2/p2/`
+(like `https://download.eclipse.org/embed-cdt/releases/6.4.0/p2/`
 and press Enter
 - select all the features in the contribution, right-click and choose
 **Fix Versions**
 - select the Contribution and **Validate**
 - select the Aggregation and **Validate**
 - stage `embededcdt.aggrcom`
 - commit with a message like:
-  - _embedcdt: update for 6.3.2_
+  - _embedcdt: update for 6.4.0_
   - _Signed-off-by: Liviu Ionescu <ilg@livius.net>_
 - click the **Commit** button (do not push yet)
 - right click, Show in local Terminal
@@ -553,13 +553,13 @@ available from:
 ### Announce release
 
 Announce the release to the **embed-cdt-dev@eclipse.org** list;
-use a subject like **Eclipse Embedded CDT plug-ins v6.3.2 released**, and
+use a subject like **Eclipse Embedded CDT plug-ins v6.4.0 released**, and
 pass a link to the release page.
 
 ## Share on Twitter
 
 - in a separate browser windows, open [TweetDeck](https://tweetdeck.twitter.com/)
 - using the `@EmbedCDT` account, enter a message like
-  **Eclipse Embedded CDT plug-ins v6.3.2 released** and on the next line
+  **Eclipse Embedded CDT plug-ins v6.4.0 released** and on the next line
   paste the link to the release
 - click the Tweet button

branding/org.eclipse.embedcdt-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-ActivationPolicy: lazy
 Bundle-Vendor: %bundle.vendor

branding/org.eclipse.embedcdt.codered-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.codered;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-ActivationPolicy: lazy
 Bundle-Vendor: %bundle.vendor

branding/org.eclipse.embedcdt.debug.gdbjtag-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.debug.gdbjtag;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-Vendor: %bundle.vendor
 Bundle-ActivationPolicy: lazy

branding/org.eclipse.embedcdt.debug.gdbjtag.jlink-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.debug.gdbjtag.jlink;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-Vendor: %bundle.vendor
 Bundle-ActivationPolicy: lazy

branding/org.eclipse.embedcdt.debug.gdbjtag.openocd-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.debug.gdbjtag.openocd;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-Vendor: %bundle.vendor
 Bundle-ActivationPolicy: lazy

branding/org.eclipse.embedcdt.debug.gdbjtag.pyocd-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.debug.gdbjtag.pyocd;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-Vendor: %bundle.vendor
 Bundle-ActivationPolicy: lazy

branding/org.eclipse.embedcdt.debug.gdbjtag.qemu-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.debug.gdbjtag.qemu;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-Vendor: %bundle.vendor
 Bundle-ActivationPolicy: lazy

branding/org.eclipse.embedcdt.debug.packs-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.debug.packs;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-ActivationPolicy: lazy
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-Vendor: %bundle.vendor

branding/org.eclipse.embedcdt.managedbuild.cross-branding/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %bundle.name
 Bundle-SymbolicName: org.eclipse.embedcdt.managedbuild.cross;singleton:=true
-Bundle-Version: 6.3.2.qualifier
+Bundle-Version: 6.4.0.qualifier
 Bundle-ActivationPolicy: lazy
 Bundle-RequiredExecutionEnvironment: JavaSE-11
 Bundle-Vendor: %bundle.vendor