Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

Le 15/10/2020 à 21:43, Rafael Fontenelle a écrit :

On Thu, Oct 15, 2020 at 2:51 PM Mario Blättermann
 wrote:


Hello all,

I've just released v4.2.0, I've succeeded to figure it out how this
works. It was simpler than expected, see below.



Great. Thanks!


Preparing a release is quite simple:

Search with grep for the current version number. You'll get some
occurrences in »configure«, »configure.ac«, »CHANGES.md« etc.
(Don't bother with the version numbers in .po file headers)
Replace the old version number with the new one.
Write an appropriate entry in CHANGES.md.
Run »autoreconf« (don't know if this is really needed).
Commit and push the changes.


Instead of editing "configure", just edit "configure.ac" and then run
"autoreconf" to recreate the "configure". For instance, changing 4.2.0
version in configure.ac will repopulate all occurrences of version in
configure.

For what it is worth, just figured out command lines to find the
current version in configure.ac and Changes:

grep '^AC_INIT' configure.ac | sed 's/.*\[\(.*\)\].*/\1/'
grep '^##' CHANGES.md | head -n1

Both should return 4.2.0 at this point.



Then, use the Gitlab web interface for creating the tag:

In the sidebar on the left, click on »Tags«. In the tag overview on
the right, click on the »New tag« button.
Fill the mask with the values for the new release:
Tag name: v4.2.0
Create from: master (just leave this entry untouched)
Message: Release 4.2.0


For command line, consider trying the following (using 4.2.0 as example):

$ git tag -a -m 'Release 4.2.0' v4.2.0

"-a" for annotation, commonly used for releases
(https://git-scm.com/docs/git-tag)

"-m " is the message you mentioned

"v4.2.0" is the tag name


Should I commit/push after this? Or the tags is added on the repo 
xithout additional commands?






That's all. Users and downstream packagers can now download the
tarball from the known location. I'll add these steps to
CONTRIBUTING.md soon.


Many thanks for these excellent instructions. I added them to 
CONTRIBUTING.md. Could you have a review to ensure they are appropriate 
and add missing ones?




I'll try to jump in and help you. How about opening an issue or merge


Great! Many thanks!


request so we can discuss ideas in there?


Bugs are opened, normally. I dont know about merge requests. Perhaps you 
need to be a member of the team to get rights on it?




Maybe we should start the CONTRIBUTING with these release
instructions, and then we adjust style and cosmetics, and add more
info later.


I agree. So far I put the instructions at the end of CONTRIBUTING.md, 
but you can move it if better.





Usually I tell then the Mageia, Opensuse and Archlinux packagers about
the new release (Fedora has its own notification service for upstream
releases). Regarding Debian, someone needs to pick up the package
maintenance.


I believe that how to contact the packagers from each distro is
something that should be added to configure as well. Something simple,
like:

## Tell package maintainers of new release

### Arch Linux:
1- Go to 
https://www.archlinux.org/packages/?sort==man-pages==
2- Choose just one between "man-pages-de", "man-pages-fr", etc.
3- Click "Flag as out-of-date"
4- Fill the comment box with the newly released version

(...)

Best regards,


Best regards,


Rafael Fontenelle

Re: Next release of manpages-l10n

[Rafael Fontenelle]

On Thu, Oct 15, 2020 at 2:51 PM Mario Blättermann
 wrote:
>
> Hello all,
>
> I've just released v4.2.0, I've succeeded to figure it out how this
> works. It was simpler than expected, see below.
>

Great. Thanks!

> Preparing a release is quite simple:
>
> Search with grep for the current version number. You'll get some
> occurrences in »configure«, »configure.ac«, »CHANGES.md« etc.
> (Don't bother with the version numbers in .po file headers)
> Replace the old version number with the new one.
> Write an appropriate entry in CHANGES.md.
> Run »autoreconf« (don't know if this is really needed).
> Commit and push the changes.

Instead of editing "configure", just edit "configure.ac" and then run
"autoreconf" to recreate the "configure". For instance, changing 4.2.0
version in configure.ac will repopulate all occurrences of version in
configure.

For what it is worth, just figured out command lines to find the
current version in configure.ac and Changes:

grep '^AC_INIT' configure.ac | sed 's/.*\[\(.*\)\].*/\1/'
grep '^##' CHANGES.md | head -n1

Both should return 4.2.0 at this point.

>
> Then, use the Gitlab web interface for creating the tag:
>
> In the sidebar on the left, click on »Tags«. In the tag overview on
> the right, click on the »New tag« button.
> Fill the mask with the values for the new release:
> Tag name: v4.2.0
> Create from: master (just leave this entry untouched)
> Message: Release 4.2.0

For command line, consider trying the following (using 4.2.0 as example):

$ git tag -a -m 'Release 4.2.0' v4.2.0

"-a" for annotation, commonly used for releases
(https://git-scm.com/docs/git-tag)

"-m " is the message you mentioned

"v4.2.0" is the tag name

>
> That's all. Users and downstream packagers can now download the
> tarball from the known location. I'll add these steps to
> CONTRIBUTING.md soon.

I'll try to jump in and help you. How about opening an issue or merge
request so we can discuss ideas in there?

Maybe we should start the CONTRIBUTING with these release
instructions, and then we adjust style and cosmetics, and add more
info later.

> Usually I tell then the Mageia, Opensuse and Archlinux packagers about
> the new release (Fedora has its own notification service for upstream
> releases). Regarding Debian, someone needs to pick up the package
> maintenance.

I believe that how to contact the packagers from each distro is
something that should be added to configure as well. Something simple,
like:

## Tell package maintainers of new release

### Arch Linux:
1- Go to 
https://www.archlinux.org/packages/?sort==man-pages==
2- Choose just one between "man-pages-de", "man-pages-fr", etc.
3- Click "Flag as out-of-date"
4- Fill the comment box with the newly released version

(...)

Best regards,
Rafael Fontenelle

Re: Next release of manpages-l10n

[Mario Blättermann]

Hello all,

I've just released v4.2.0, I've succeeded to figure it out how this
works. It was simpler than expected, see below.

Am So., 4. Okt. 2020 um 10:29 Uhr schrieb Jean-Philippe MENGUAL
:
>
>
> Le 04/10/2020 à 07:32, Helge Kreutzmann a écrit :
> > Hello Jean-Philippe,
> > On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:
> >> Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
> >> :
> >> 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.
> >
> > I strongly concour with Mario.
> >
> > manpages-l10n uses Debian infrastructure, but it is not a Debian
> > project, but rather an upstream one.
> >
> > There are various downstreams as Mario gave a nice overview.
> >
> > One of them is Debian, where currently Tobias is the Maintainer.
> > Unfortunately Tobias is not able to maintain both the Debian
> > downstream and the upstream project as he used to be.
> >
> > Mario is very involved in getting the upstream part working again
> > (which I stronly support where I technically can) and we are
> > discussing this (albeit very slowly) with Tobias.
> >
> > I offered to take over the Debian downstream part, which I technically
> > could (though reviewing the steps once more especially for backports
> > could be helpful), but I'm no developer, so Tobias would need to grant
> > me the permission for uploads. This has been proposed to Tobias, so I
> > hope the Debian side gets going properly again as well.
> >
> > But the big issue are the upstream releases.
>
> Can Tobias, Mario and whoever write a step-to-step doc (eg. in
> CONTRIBUTING.md) with administrative commands and actions needed to be a
> release manager? Perhaps I can help if I have the process and the git
> commands written, if I know who announce the next release to, etc. In
> case I have technical issues, I may find help on the mailing lists. But
> this initial doc is absolutely needed to help a non-tech person to do
> the release management I think.
>
Preparing a release is quite simple:

Search with grep for the current version number. You'll get some
occurrences in »configure«, »configure.ac«, »CHANGES.md« etc.
(Don't bother with the version numbers in .po file headers)
Replace the old version number with the new one.
Write an appropriate entry in CHANGES.md.
Run »autoreconf« (don't know if this is really needed).
Commit and push the changes.

Then, use the Gitlab web interface for creating the tag:

In the sidebar on the left, click on »Tags«. In the tag overview on
the right, click on the »New tag« button.
Fill the mask with the values for the new release:
Tag name: v4.2.0
Create from: master (just leave this entry untouched)
Message: Release 4.2.0

That's all. Users and downstream packagers can now download the
tarball from the known location. I'll add these steps to
CONTRIBUTING.md soon.

Usually I tell then the Mageia, Opensuse and Archlinux packagers about
the new release (Fedora has its own notification service for upstream
releases). Regarding Debian, someone needs to pick up the package
maintenance.

Best Regards,
Mario

Re: Next release of manpages-l10n

[Helge Kreutzmann]

Hello Jean-Philippe,
On Sun, Oct 04, 2020 at 10:28:59AM +0200, Jean-Philippe MENGUAL wrote:
> Le 04/10/2020 à 07:32, Helge Kreutzmann a écrit :
> > On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:
> > > Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
> > > :

> Can Tobias, Mario and whoever write a step-to-step doc (eg. in
> CONTRIBUTING.md) with administrative commands and actions needed to be a
> release manager? Perhaps I can help if I have the process and the git
> commands written, if I know who announce the next release to, etc. In case I
> have technical issues, I may find help on the mailing lists. But this
> initial doc is absolutely needed to help a non-tech person to do the release
> management I think.

Yes, this is the missing piece in the puzzle. Once we have this, I
think Mario is able to do the most generic (upstream) parts as well
and I would be able to complete the Debian specific parts.

Greetings

Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

Le 04/10/2020 à 07:32, Helge Kreutzmann a écrit :

Hello Jean-Philippe,
On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:

Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
:
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.


I strongly concour with Mario.

manpages-l10n uses Debian infrastructure, but it is not a Debian
project, but rather an upstream one.

There are various downstreams as Mario gave a nice overview.

One of them is Debian, where currently Tobias is the Maintainer.
Unfortunately Tobias is not able to maintain both the Debian
downstream and the upstream project as he used to be.

Mario is very involved in getting the upstream part working again
(which I stronly support where I technically can) and we are
discussing this (albeit very slowly) with Tobias.

I offered to take over the Debian downstream part, which I technically
could (though reviewing the steps once more especially for backports
could be helpful), but I'm no developer, so Tobias would need to grant
me the permission for uploads. This has been proposed to Tobias, so I
hope the Debian side gets going properly again as well.

But the big issue are the upstream releases.


Can Tobias, Mario and whoever write a step-to-step doc (eg. in 
CONTRIBUTING.md) with administrative commands and actions needed to be a 
release manager? Perhaps I can help if I have the process and the git 
commands written, if I know who announce the next release to, etc. In 
case I have technical issues, I may find help on the mailing lists. But 
this initial doc is absolutely needed to help a non-tech person to do 
the release management I think.


Regards



Greetings

 Helge

Re: Next release of manpages-l10n

[Helge Kreutzmann]

Hello Jean-Philippe,
On Sat, Oct 03, 2020 at 08:25:36PM +0200, Mario Blättermann wrote:
> Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
> :
> 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.

I strongly concour with Mario.

manpages-l10n uses Debian infrastructure, but it is not a Debian
project, but rather an upstream one. 

There are various downstreams as Mario gave a nice overview.

One of them is Debian, where currently Tobias is the Maintainer.
Unfortunately Tobias is not able to maintain both the Debian
downstream and the upstream project as he used to be. 

Mario is very involved in getting the upstream part working again
(which I stronly support where I technically can) and we are
discussing this (albeit very slowly) with Tobias.

I offered to take over the Debian downstream part, which I technically
could (though reviewing the steps once more especially for backports
could be helpful), but I'm no developer, so Tobias would need to grant
me the permission for uploads. This has been proposed to Tobias, so I
hope the Debian side gets going properly again as well.

But the big issue are the upstream releases.

Greetings

Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Re: Next release of manpages-l10n

[Helge Kreutzmann]

Hello Jean-Philippe,
On Sat, Oct 03, 2020 at 08:03:06PM +0200, Jean-Philippe MENGUAL wrote:
> Le 03/10/2020 à 19:52, Mario Blättermann a écrit :
> > Hello,
> > 
> > Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
> > :
> > > 
> > > Hi,
> > > 
> > > What about the release and a Debian package? I still don't see any
> > > package in the Debian repo.
> > 
> > The manpages-*_4.1.0 packages are present in Sid (but not in Buster 
> > backports):
> > https://packages.debian.org/de/source/sid/manpages-l10n
> 
> hmmm. A Google search plus a apt-cache search manpages-l10n (or show) does
> not return anything. Maybe there is not binary yet? Why?

I do have it for German in Testing:
ii  manpages-de4.1.0-1  all  German manpages

Similarly I could install this version of manpages-fr.

As Mario said, if possible I would try to make a backports upload
later, if Tobias can transfer the necessary knowledge and rights to
me.

Greetings

Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

Le 03/10/2020 à 20:03, Jean-Philippe MENGUAL a écrit :

Hi,

Le 03/10/2020 à 19:52, Mario Blättermann a écrit :

Hello,

Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
:


Hi,

What about the release and a Debian package? I still don't see any
package in the Debian repo.


The manpages-*_4.1.0 packages are present in Sid (but not in Buster 
backports):

https://packages.debian.org/de/source/sid/manpages-l10n


hmmm. A Google search plus a apt-cache search manpages-l10n (or show) 
does not return anything. Maybe there is not binary yet? Why?


Oh I understand. I thought we would have a manpages-l10n, but no. The 
choice is to generate, from the source, several binaries for each 
language. It is a good idea to avoid peple having useless binaries as 
not in their language.


So now it is clear for me.






We are not yet at freeze time, but probably
we should try to release a package?



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.

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!


ok now things are clear for me, I guess creating a new Debian package 
would be more confortable from a release point upstream. When such 
milestone is exptected? I think from this milestone, I can update the 
Debian source package, then submitting to Helge as uploader.





Regards




Thanks in advance,
Mario



Regards



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?

Regards



Of 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

Re: Next release of manpages-l10n

[Mario Blättermann]

Hello Jean-Philippe,

Am Sa., 3. Okt. 2020 um 20:03 Uhr schrieb Jean-Philippe MENGUAL
:
>
> Hi,
>
> Le 03/10/2020 à 19:52, Mario Blättermann a écrit :
> > Hello,
> >
> > Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
> > :
> >>
> >> Hi,
> >>
> >> What about the release and a Debian package? I still don't see any
> >> package in the Debian repo.
> >
> > The manpages-*_4.1.0 packages are present in Sid (but not in Buster 
> > backports):
> > https://packages.debian.org/de/source/sid/manpages-l10n
>
> hmmm. A Google search plus a apt-cache search manpages-l10n (or show)
> does not return anything. Maybe there is not binary yet? Why?
>
There's no binary package named manpages-l10n. The source package gets
split in the usual packages manpages-fr, manpages-fr-dev, manpages-de,
manpages-de-dev and so on. By choosing the existing names, we get a
proper upgrade path and avoid that users will be forced to install
lots of man pages in other languages – which would happen in an
all-in-one package of manpages-l10n.

> >
> >> We are not yet at freeze time, but probably
> >> we should try to release a package?
> >>
> >
> > 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.
> >
> > 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,
Mario


>
> Regards
>
>
> >
> > Thanks in advance,
> > Mario
> >
> >
> >> Regards
> >>
> >>
> >>
> >> 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 

Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

Hi,

Le 03/10/2020 à 19:52, Mario Blättermann a écrit :

Hello,

Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
:


Hi,

What about the release and a Debian package? I still don't see any
package in the Debian repo.


The manpages-*_4.1.0 packages are present in Sid (but not in Buster backports):
https://packages.debian.org/de/source/sid/manpages-l10n


hmmm. A Google search plus a apt-cache search manpages-l10n (or show) 
does not return anything. Maybe there is not binary yet? Why?





We are not yet at freeze time, but probably
we should try to release a package?



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.

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!


Regards




Thanks in advance,
Mario



Regards



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?

Regards



Of 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

Re: Next release of manpages-l10n

[Mario Blättermann]

Hello,

Am Sa., 3. Okt. 2020 um 16:15 Uhr schrieb Jean-Philippe MENGUAL
:
>
> Hi,
>
> What about the release and a Debian package? I still don't see any
> package in the Debian repo.

The manpages-*_4.1.0 packages are present in Sid (but not in Buster backports):
https://packages.debian.org/de/source/sid/manpages-l10n

> We are not yet at freeze time, but probably
> we should try to release a package?
>

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.

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.

Thanks in advance,
Mario


> Regards
>
>
>
> 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?
> >
> > Regards
> >
> >>
> >> Of 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
> >>
> >>

Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

Hi,

What about the release and a Debian package? I still dont see any 
package in the Debian repo. We are not yet at freeze time, but probably 
we should try to release a package?


Regards



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?


Regards



Of 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

Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

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?


Regards



Of 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

Re: Next release of manpages-l10n

[Mario Blättermann]

Hello,

Am Fr., 29. Mai 2020 um 21:12 Uhr schrieb Helge Kreutzmann
:
>
> 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?
>
Yes, let's keep the releases about every three months. This is a fair
compromise between being strictly up-to-date and a comfortable
workflow for both translators and downstream packagers.

The recently imported Italian translations should be disabled for the
time being. I've written to Marco Curreli that after completion of the
import, maybe in a few weeks, the next release then will include the
Italian translations. Until then we have to solve a problem: Although
not visible at the project page, the version 5.06 of manpages-it has
been released. It is available from Bitbucket [1], and at least Mageia
has already updated the package to this version. This means, to get a
proper upgrade path, we need to update manpages-l10n to a version
number greater than 5.06, or force downstream packagers to use »Epoch«
mechanisms.

> 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.
>
> Of 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.
>
The package manpages-l10n-4.0.0 is already in Fedora Rawhide, based on
a Git checkout. But it is far from being complete. That time, our
package list was not up-to-date, and there were some problems with
involving the Fedora man pages in the update mechanisms. Should be
solved now.

[1]  https://bitbucket.org/marco.it/man-pages-it/downloads/

Best Regards,
Mario

Re: Next release of manpages-l10n

[Helge Kreutzmann]

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.

Of 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


-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Re: Next release of manpages-l10n

[Dr. Tobias Quathamer]

Am 10.02.20 um 10:10 schrieb Mario Blättermann:
> Hello,
> 
> 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!

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

Hi,

Le 11/02/2020 à 02:48, Mario Blättermann a écrit :

Hello Jean-Philippe,

Jean-Philippe MENGUAL > schrieb am Di., 11. Feb. 2020, 01:15:


Hi,

Great news, congrats! I am happy to see this package alive.

Who can push in the fr subdir of the tree? Can we add people manually,
even if not DDs? Some of the most important French translators are not
DDs, but would make sense they can push the translations to fr.


No problem, people without a DD account can simply create a guest 
developer account at [1] and then apply for membership at [2]. All 
project members registered as "maintainer" (you too) are then allowed to 
accept the new translators.


Ok perfect, the relevant persons were added.



But note: Never commit anything outside of your own directory (po/fr/ in 
your case) without discussing the change with us, unless our scripts 
change something in templates/ or wherever else. Another exception are 
the localized files in public/ (which feed the status pages), if you 
found some wrong translation there.


ok no problem, I will follow what the French team will say from their 
experience and in case of doubt, will ask here


Sincerely



[1] https://signup.salsa.debian.org/ 
[2] https://salsa.debian.org/manpages-l10n-team/manpages-l10n 



Best Regards,
Mario



Regards



Jean-Philippe MENGUAL

Le 10/02/2020 à 10:10, Mario Blättermann a écrit :
 > Hello,
 >
 > 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.
 >
 > This means, you should now complete all the work you are already
 > started with. In the meantime, we will update the translation
 > templates and the existing *.po files as usual. Due to some version
 > changes in our supported packages, such updates can happen more often
 > than expected. For example, the original »manpages« package has been
 > recently updated to v5.05. Once the distribution packages have been
 > arrived, we will do an extra update. Please always work on the latest
 > *.po files from the Git repository, sorry for the inconvenience.
 > Because we support lots of distribution packages whose updates we
 > can't influence, we are unable to declare a »string freeze« in common
 > sense.
 >
 > In case of the *.po file you are working on is older than the latest
 > template from the Git repository, you can easily update it as follows
 > (regardless of it's really older):
 >
 > Copy your *.po file to the right place in your local copy of the Git
 > repo. Committing is not needed for the time being.
 >
 > Run the following script in the po/ directory of your language:
 >
 > ./update-po.sh relative/path/to/your/po/file
 >
 > For example:
 >
 > ./update-po.sh man1/chroot.1.po
 >
 > The script merges your *.po file with both the latest template (*.pot
 > file) and the compendium files (common/*.po). Besides that, it
removes
 > unused gettext messages at the end of the file and deletes old msgid
 > comments (starting with #|), as long as the appropriate gettext
 > message is no longer marked as »fuzzy«.
 >
 > Happy translating!
 >
 > Best Regards,
 > Mario
 >

Re: Next release of manpages-l10n

[Mario Blättermann]

Hello Jean-Philippe,

Jean-Philippe MENGUAL  schrieb am Di., 11. Feb. 2020,
01:15:

> Hi,
>
> Great news, congrats! I am happy to see this package alive.
>
> Who can push in the fr subdir of the tree? Can we add people manually,
> even if not DDs? Some of the most important French translators are not
> DDs, but would make sense they can push the translations to fr.
>

No problem, people without a DD account can simply create a guest developer
account at [1] and then apply for membership at [2]. All project members
registered as "maintainer" (you too) are then allowed to accept the new
translators.

But note: Never commit anything outside of your own directory (po/fr/ in
your case) without discussing the change with us, unless our scripts change
something in templates/ or wherever else. Another exception are the
localized files in public/ (which feed the status pages), if you found some
wrong translation there.

[1] https://signup.salsa.debian.org/
[2] https://salsa.debian.org/manpages-l10n-team/manpages-l10n

Best Regards,
Mario



> Regards
>
>
>
> Jean-Philippe MENGUAL
>
> Le 10/02/2020 à 10:10, Mario Blättermann a écrit :
> > Hello,
> >
> > 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.
> >
> > This means, you should now complete all the work you are already
> > started with. In the meantime, we will update the translation
> > templates and the existing *.po files as usual. Due to some version
> > changes in our supported packages, such updates can happen more often
> > than expected. For example, the original »manpages« package has been
> > recently updated to v5.05. Once the distribution packages have been
> > arrived, we will do an extra update. Please always work on the latest
> > *.po files from the Git repository, sorry for the inconvenience.
> > Because we support lots of distribution packages whose updates we
> > can't influence, we are unable to declare a »string freeze« in common
> > sense.
> >
> > In case of the *.po file you are working on is older than the latest
> > template from the Git repository, you can easily update it as follows
> > (regardless of it's really older):
> >
> > Copy your *.po file to the right place in your local copy of the Git
> > repo. Committing is not needed for the time being.
> >
> > Run the following script in the po/ directory of your language:
> >
> > ./update-po.sh relative/path/to/your/po/file
> >
> > For example:
> >
> > ./update-po.sh man1/chroot.1.po
> >
> > The script merges your *.po file with both the latest template (*.pot
> > file) and the compendium files (common/*.po). Besides that, it removes
> > unused gettext messages at the end of the file and deletes old msgid
> > comments (starting with #|), as long as the appropriate gettext
> > message is no longer marked as »fuzzy«.
> >
> > Happy translating!
> >
> > Best Regards,
> > Mario
> >
>
>

Re: Next release of manpages-l10n

[Jean-Philippe MENGUAL]

Hi,

Great news, congrats! I am happy to see this package alive.

Who can push in the fr subdir of the tree? Can we add people manually, 
even if not DDs? Some of the most important French translators are not 
DDs, but would make sense they can push the translations to fr.


Regards



Jean-Philippe MENGUAL

Le 10/02/2020 à 10:10, Mario Blättermann a écrit :

Hello,

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.

This means, you should now complete all the work you are already
started with. In the meantime, we will update the translation
templates and the existing *.po files as usual. Due to some version
changes in our supported packages, such updates can happen more often
than expected. For example, the original »manpages« package has been
recently updated to v5.05. Once the distribution packages have been
arrived, we will do an extra update. Please always work on the latest
*.po files from the Git repository, sorry for the inconvenience.
Because we support lots of distribution packages whose updates we
can't influence, we are unable to declare a »string freeze« in common
sense.

In case of the *.po file you are working on is older than the latest
template from the Git repository, you can easily update it as follows
(regardless of it's really older):

Copy your *.po file to the right place in your local copy of the Git
repo. Committing is not needed for the time being.

Run the following script in the po/ directory of your language:

./update-po.sh relative/path/to/your/po/file

For example:

./update-po.sh man1/chroot.1.po

The script merges your *.po file with both the latest template (*.pot
file) and the compendium files (common/*.po). Besides that, it removes
unused gettext messages at the end of the file and deletes old msgid
comments (starting with #|), as long as the appropriate gettext
message is no longer marked as »fuzzy«.

Happy translating!

Best Regards,
Mario