Merge pull request #251 from matks/improve-release-process

Improve release process: publish release note after upgrade API

content/maintainers-guide/processes/release/prestashop/final-steps.md

@@ -33,6 +33,10 @@ For new major/minor version you will have to create a new dedicated branch node.
 
 Once this step is done, update the Release Tracker GitHub issue by ticking the "Available for upgrade" box.
 
+{{% notice tip %}}
+The release note announcing the new version can be published after this change is effective. Please verify https://api.prestashop.com/xml/channel.xml file status. You might need to wait for the cache to be cleared.
+{{% /notice %}}
+
 ## 2. Create Docker images for the new version
 
 * Checkout the [project][docker-repository], install the project and create a new branch

content/maintainers-guide/processes/release/prestashop/release-publicly.md

@@ -101,4 +101,8 @@ It's not unusual to have very long changelogs, especially in minor versions. To
 Congratulations! You can now update the Release Tracker GitHub issue: tick the "QA" and "Development" boxes and [add a comment](https://github.com/PrestaShop/PrestaShop/issues/19959#issuecomment-653083656).
 
 
+{{% notice tip %}}
+In the past, we used to publish the release note at this step of the release process. Please keep it on hold a little longer and do it after the Update API stream for 1-click upgrade has been updated.
+{{% /notice %}}
+
 [git-tag]: https://git-scm.com/book/en/v2/Git-Basics-Tagging