From 8bf362838e9ef991452afc2ae3ae2e91d915d600 Mon Sep 17 00:00:00 2001 From: Alexandre Alapetite Date: Sun, 18 Jun 2023 23:05:28 +0200 Subject: Update dev dependencies (#5478) --- docs/en/developers/05_Release_new_version.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/en/developers') diff --git a/docs/en/developers/05_Release_new_version.md b/docs/en/developers/05_Release_new_version.md index 46bec973c..ef69084ae 100644 --- a/docs/en/developers/05_Release_new_version.md +++ b/docs/en/developers/05_Release_new_version.md @@ -3,7 +3,7 @@ In order to get as much feedback as possible before a release, it’s preferable to announce it on GitHub by creating a dedicated ticket ([see examples](https://github.com/FreshRSS/FreshRSS/search?utf8=%E2%9C%93&q=Call+for+testing&type=Issues)). This should be done **at least one week in advance**. -It’s also recommended to make the announcement on mailing@freshrss.org. +It’s also recommended to make the announcement on . ## Check the dev status @@ -95,7 +95,7 @@ When everything’s working, it’s time to announce the release to the world! * on GitHub by creating[a new release](https://github.com/FreshRSS/FreshRSS/releases/new) * on the freshrss.org blog, at least for stable versions (write the article on[FreshRSS/freshrss.org](https://github.com/FreshRSS/freshrss.org)) * on Twitter ([@FreshRSS](https://twitter.com/FreshRSS) account) -* and on mailing@freshrss.org +* and on ## Starting the next development version -- cgit v1.2.3