Change release process details for blog.torproject.org
blog.torproject.org moved from drupal to a static website: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/blog#how-to-write-a-new-blog-post-in-gitlab
We need to update our release process so that it gives us the right details. In particular:
- The RM needs to have a user on gitlab.torproject.org; shall we have a shared one or individual ones?
- Our tooling (
./bin/generate-Tor-blog-post
) must produce valid markdown, not HTML; yesterday I used this online tool, which was good enough in my case, but we probably want a more robust solution for the future!
See the details for Tails 5.0: https://gitlab.torproject.org/tpo/web/blog/-/merge_requests/62 + https://gitlab.torproject.org/tpo/web/blog/-/commit/8233b79718cd2133fe0ec536e90d9867b2215c4b
The problem will popup again at the next major release
Edited by boyska