Indeed, especially to do justice to the needs of our supported Rolling Releases (Debian Sid, Opensuse Tumbleweed, Archlinux) we should try to release every three months, and the latest release was three months ago. Two weeks ago I wrote to Tobias Quathamer, asking him to tell me the steps of a release, so that I would become able to do releases myself. He didn't respond yet. As I already knew, actually he doesn't have the time anymore to contribute to manpages-l10n, neither for translations and the release management nor for maintaining the Debian packages. In the past months, I took some administrative tasks over, like updates from upstream packages, updating the authors list, testing the committed .po files for formatting issues and so on. But I don't have any Autotools skills, so I haven't tried to roll out a release yet. This means, first we need a new release manager. Someone who's willing and able to handle the Autotools stack, create the release tarball, and if needed, to fix things if something fails. Second, the Debian part needs a new package maintainer. The German translator Helge Kreutzmann already said that he would take this over, at least as a co-maintainer. Packages for the other distributions are actively maintained, except for Archlinux, but I maintain some (Git-based) unofficial packages in the Arch Linux User Repository, this is OK so far.
While I can help Helge for the Debian package (downstream), I dont have skills myself to be a release manager upstream. While I may do some checks, I dont know git enough to do milestones, tarballs, and do things cleanly. I am not a technician at all.
Regards
That's why I call for a volunteer for this task! He would probably need to get the »owner« state in the Salsa repo, but this shouldn't be the problem.hmmm. Thanks for this message, raising very important information. I am not an uploading devloper, but I would like to search for an idea. If anyone in the l10n teams has an iedea too, welcome!You don't have to be an »uploading developer« for releasing an upstream tarball of manpages-l10n. This is only for Debian packaging. Upstream releasing and downstream packaging do not necessarily have to be linked to each other. Of course, this can be done by different persons, although manpages-l10n is still to be considered as a Debian project, but meanwhile distribution-agnostic. Best Regards, MarioRegardsThanks in advance, MarioRegards Jean-Philippe MENGUAL Debian Developer non uploading Community team member Accessibility team member debian-l10n-french team member President of Debian France non-profit organization Le 30/05/2020 à 08:27, Jean-Philippe MENGUAL a écrit :Le 29/05/2020 à 21:12, Helge Kreutzmann a écrit :Hello Tobias, On Sat, Apr 04, 2020 at 09:40:41PM +0200, Dr. Tobias Quathamer wrote:Am 10.02.20 um 10:10 schrieb Mario Blättermann:the manpages-l10n project is now almost ready for a release. The new version 4.0 is scheduled for march 1, 2020. All commits prior to this date will be included in the tarball.Hi all, the new package manpages-l10n has just been accepted into Debian unstable. Thanks for all your work!Thank you very much for your work and the scripts as well. I discussed this with Mario and we think it would be a good time to target the next version, now with some more languages (I guess Mario has a better overview of the stats) maybe in about a week? I just checked with the French team, this release would close also the remaining open Debian bugs for manpages-fr. And afterwards a Debian backport would be nice.What would bu useful, if possible, is having a schedule of releases, to know when will be the latest release before the freeze for Bullseye. We still hope to finish the updating work before Bullseye. What is the absolute deadline for it? RegardsOf course, the other supported (and unsupported) distribution might also use the chance to do the update, e.g. for Fedora for the very first time. Greetings Helge