Synchronize releasing.md

Change-Id: I19dc3c73b28c3ecf8292f63805063cd6124095a9

RELEASING.md

@@ -8,8 +8,11 @@ EPP releases happen for each milestone and release candidate according to the [E
 
 **Steps at the beginning of each release cycle (i.e. before M1):**
 
+This checklist is only used once per release cycle. Scroll down for the per-milestone/RC steps.
+
 - [ ] Create new [PMI entry](https://projects.eclipse.org/projects/technology.packaging)
 - [ ] Add Target Milestones in [Bugzilla](https://dev.eclipse.org/committers/bugs/bugz_manager.php)
+- [ ] Look at renaming zips for mac
 - [ ] Update splash screen (once per release cycle, hopefully done before M1). See detailed [instructions](https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/tree/packages/org.eclipse.epp.package.common/splash/INSTRUCTIONS.md). For 2022-06 see Bug [575781](https://bugs.eclipse.org/bugs/show_bug.cgi?id=575781) for new splash screens.
 - [ ] When the year changes, e.g. between 2019-12 and 2020-03 releases, an update of the copyright year is required with a very smart search&replace. A good replacement is `/, 2021/, 2022/` excluding `*.svg`
 - [ ] In addition to the "Update Name" step on every M and RC, the whole version string is updated, including platform version; this is a large change including
@@ -31,7 +34,6 @@ EPP releases happen for each milestone and release candidate according to the [E
 **Steps for all Milestones and RCs:**
 
 - [ ] Check for bad links to Bugzilla (other things?) especially in `epp.website.xml`
-- [ ] Look at renaming zips for mac
 - [ ] Make sure any outstanding reviews are progressing - e.g. file IP logs, get PMC approval, etc.
   - For 2022-03 there is no review planned, next review expected to be a progress review around 2022-06
 - [ ] Ensure that the [CI build](https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/) is green<!-- or yellow (yellow means some files have failed to notarize which can be handled later on in this process)-->. Resolving non-green builds will require tracking down problems and incompatibilities across all Eclipse participating projects. [cross-project-issues-dev](https://accounts.eclipse.org/mailing-list/cross-project-issues-dev) mailing list is a good place to start when tracking such problems.
@@ -77,7 +79,7 @@ EPP releases happen for each milestone and release candidate according to the [E
   - [ ] Help -> About says expected build name and milestone, e.g. `2020-03-M2`
   - [ ] `org.eclipse.epp.package.*` features and bundles have the timestamp of the forced qualifier update or later
   - [ ] Upgrade from previous release works. To test the upgrade an equivalent to the simrel release composite site needs to done. Add the following software sites to available software, check for updates and then make sure stuff works. In particular check error log and that core features (Such as JDT, Platform) have been upgraded.
-    - `https://download.eclipse.org/staging/2022-12/` - _NOTE_ Use `SIMREL_REPO` if the staging repo has been updated since the `SIMREL_REPO` location was created.
+    - `https://download.eclipse.org/staging/2023-03/` - _NOTE_ Use `SIMREL_REPO` if the staging repo has been updated since the `SIMREL_REPO` location was created.
     - `https://download.eclipse.org/technology/epp/staging/repository/`
   - [ ] Verify no non-EPP content is in the p2 repo (especially justj, update [remove-justj-from-p2.xml](https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/tree/releng/org.eclipse.epp.config/tools/remove-justj-from-p2.xml) if needed)
 - [ ] Edit the [Jenkins build](https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/)