Re: Next release of manpages-l10n
On Thu, Oct 15, 2020 at 2:51 PM Mario Blättermann
<mario.blaettermann@gmail.com> 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=&q=man-pages&maintainer=&flagged=
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
Reply to: