Automating release process #1631
Replies: 28 comments
-
|
I wrote a script that executes the steps 3 & 4 in above and pushes the changes. It runs on the translation server and automatically pushes changes based on new translations using a "deploy key" registered on GitHub. It may be run periodically, e.g. once a week. Here is an example of the result of running it on my fork. Changes to the translation server can be tampered with or mishandled, so they need to be checked by human eyes before being merged into the main branch (if a problem is found, we have to correct the translation on the translation server and wait for the next push by the automatic execution). That's why the new branch is created instead of direct commits on the main branch. The point is that translation changes are always made on the translation server before being reflected in the repository. There are no changes in the reverse direction. However, direction is reversed for translation templates ( |
Beta Was this translation helpful? Give feedback.
-
|
Now update of translation will be pushed every Monday into the |
Beta Was this translation helpful? Give feedback.
-
|
@racke, I could automate the steps 7 to 9 (making source distribution) using GitHub workflow:
I'm not sure if these results are the same as what you are aiming for, but if this helps, please use it. In above, the resulting source distribution files are stored in temporary storage, but they can also be uploaded to the release page automatically. Please let me know if you want me to update the workflow file. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I will check that, |
Beta Was this translation helpful? Give feedback.
-
Automating release notes?Automatically generated release notes look enough for me (animation). Currently we create a branch for release notes (e.g. (Afaik the original intention of creating such a branch was to be able to know about noteworthy changes in advance. However, since people complains about them after the new release without debugging them in advance anyway, I feel editing the release notes manually seems a waste of effort. Really interested people will look at the PRs and milestones.) |
Beta Was this translation helpful? Give feedback.
-
|
Looks good to me ... I will try that out ASAP. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I'm ready for the release. Is NEWS.md up to date? |
Beta Was this translation helpful? Give feedback.
-
|
It looks up-to-date for me, except the release date 😃 |
Beta Was this translation helpful? Give feedback.
-
|
Yes. will fix that. |
Beta Was this translation helpful? Give feedback.
-
|
OK release prepared in GitHub. @ikedas please take a look. Will release it tomorrow. |
Beta Was this translation helpful? Give feedback.
-
|
It looks good for me. |
Beta Was this translation helpful? Give feedback.
-
|
Released on GitHub. How did you produce the message for the mailing list? |
Beta Was this translation helpful? Give feedback.
-
|
In my case, I have copied the HTML |
Beta Was this translation helpful? Give feedback.
-
|
fyi: On the new mailing list server, the list for translators (ex. lets@translate.sympa.org) is included in the announcement list, so you may send annuncement only to |
Beta Was this translation helpful? Give feedback.
-
|
@racke, FYI I wrote a script to generate MIME message:
|
Beta Was this translation helpful? Give feedback.
-
|
OK thanks will look at that as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@ikedas done |
Beta Was this translation helpful? Give feedback.
-
Unfortunately it barfs: open body: Invalid argument at /usr/share/perl5/MIME/Entity.pm line 1892. |
Beta Was this translation helpful? Give feedback.
-
|
What is the version of MIME-Tools ? |
Beta Was this translation helpful? Give feedback.
-
|
@racke, please try this: $ diff -u support/github-release-message.pl.orig support/github-release-message.pl
--- support/github-release-message.pl.orig 2022-11-18 22:29:49.533269207 +0900
+++ support/github-release-message.pl 2022-11-18 22:28:03.677540670 +0900
@@ -24,6 +24,7 @@
my $release = decode_json($json);
my $plain = sprintf "%s\n====\n\n%s", $release->{name}, $release->{body};
+Encode::_utf8_off($plain);
my $html =
sprintf
"<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\"/>\n<title>%s</title>\n</head>\n<body>%s</body>\n</html>", |
Beta Was this translation helpful? Give feedback.
-
|
I extended the script with SMTP and wrapping all links with <a href .... To unsubscribe from this list, click here: /auto_signoff/announce?email=racke%40linuxia.de I will clean up the script and send it to you. |
Beta Was this translation helpful? Give feedback.
-
|
This seems the bug in Sympa. Once you have improved the script to some extent, you can put it under /support/. Anyway, thank you so much for the release work! 🎉 |
Beta Was this translation helpful? Give feedback.
-
Can you open a bug report :-). |
Beta Was this translation helpful? Give feedback.
-
Some ideas
|
Beta Was this translation helpful? Give feedback.
-
|
Release drafter sounds like a good idea. I also think that the the [ready] label should put on the PR. |
Beta Was this translation helpful? Give feedback.
-
Discussion about automating release process.
Resources
support/README.support.mdin source repo)Beta Was this translation helpful? Give feedback.
All reactions