diff options
| author |  Alexandre Alapetite <alexandre@alapetite.fr>
| 2023-06-18 23:05:28 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2023-06-18 23:05:28 +0200 |
| commit | 8bf362838e9ef991452afc2ae3ae2e91d915d600 (patch) | |
| tree | 263f8c529f4f5aeb53b0eddd8e807eb1106bd310 /docs | |
| parent | 723f7577d0a388a90779930754c5aacb9f66b168 (diff) | |
Update dev dependencies (#5478)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/en/developers/05_Release_new_version.md | 4 | ||||
| -rw-r--r-- | docs/fr/developers/05_Release_new_version.md | 4 |
2 files changed, 4 insertions, 4 deletions
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 <mailing@freshrss.org>. ## 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 <mailing@freshrss.org> ## Starting the next development version diff --git a/docs/fr/developers/05_Release_new_version.md b/docs/fr/developers/05_Release_new_version.md index 54c78137a..c9c4e9389 100644 --- a/docs/fr/developers/05_Release_new_version.md +++ b/docs/fr/developers/05_Release_new_version.md @@ -5,7 +5,7 @@ de l’annoncer sur GitHub en créant un ticket dédié ([voir les exemples](https://github.com/FreshRSS/FreshRSS/search?utf8=%E2%9C%93&q=Call+for+testing&type=Issues)). Ceci est à faire **au moins une semaine à l’avance**. -Il est aussi recommandé de faire l’annonce sur mailing@freshrss.org. +Il est aussi recommandé de faire l’annonce sur <mailing@freshrss.org>. ## S’assurer de l’état de dev @@ -139,7 +139,7 @@ Lorsque tout fonctionne, il est temps d’annoncer la sortie au monde entier ! l’article sur [FreshRSS/freshrss.org](https://github.com/FreshRSS/freshrss.org)). * sur Twitter (compte [@FreshRSS](https://twitter.com/FreshRSS)) ; -* et sur mailing@freshrss.org ; +* et sur <mailing@freshrss.org> ; ## Lancer la prochaine version de développement |