maint.mk: announcement should not be emailed to the TP when there are no changes

maint.mk: announcement should not be emailed to the TP when there are no changes

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

I am maintaining a2ps, and have recently been making frequent alpha
releases as I attempt to stabilise the result of a massive updating effort
after a long period of quiescence.

The most recent release involves no changes to the gettext strings.

Using the standard gnulib release procedure for GNU projects,
coordinator@translationproject.org is automatically emailed for each
release, but apparently this is not desired. I received this from Benno
Schulenberg <coordinator@translationproject.org>:

My scripts find zero changes in the msgids.
>
> When there are no changes in the POT file, there is no need
> to announce the (pre)release to me -- it just creates extra,
> unneeded work for me.
>

Of course, I can try to catch this manually, but I presume other projects
are also sending unwanted email like this (unless I'm doing something
wrong?); can something be done in gnulib?

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 2023 bytes --]

Re: maint.mk: announcement should not be emailed to the TP when there are no changes

[Simon Josefsson via Gnulib discussion list]

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

Reuben Thomas <rrt@sc3d.org> writes:

> Using the standard gnulib release procedure for GNU projects,
> coordinator@translationproject.org is automatically emailed for each
> release, but apparently this is not desired. I received this from Benno
> Schulenberg <coordinator@translationproject.org>:
>
> My scripts find zero changes in the msgids.
>>
>> When there are no changes in the POT file, there is no need
>> to announce the (pre)release to me -- it just creates extra,
>> unneeded work for me.
>>
>
> Of course, I can try to catch this manually, but I presume other projects
> are also sending unwanted email like this (unless I'm doing something
> wrong?); can something be done in gnulib?

I manually remove that Cc when not appropriate, or add the following to
cfg.mk for projects without translations:

translation_project_ =

however I realize this is manual work, so I agree with you it could be
improved.

To automatically understand if a cc to the translation project is
necessary or not, I think we'd need access to the previously sent pot
file, no?  I guess we could wget that from somewhere and compare it, but
that seems a bit fragile.  I generally don't like fetching files from
the Internet durings builds, so another approach is to store them in git
and make a comparison there.

Sorry, no real answer, but just some additional thoughts.

/Simon

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

Re: maint.mk: announcement should not be emailed to the TP when there are no changes

[Reuben Thomas]

[-- Attachment #1: Type: text/plain, Size: 541 bytes --]

On Sat, 4 Feb 2023 at 21:18, Simon Josefsson <simon@josefsson.org> wrote:

>
> To automatically understand if a cc to the translation project is
> necessary or not, I think we'd need access to the previously sent pot
> file, no?  I guess we could wget that from somewhere and compare it, but
> that seems a bit fragile.  I generally don't like fetching files from
> the Internet durings builds, so another approach is to store them in git
> and make a comparison there.
>

Thanks, I hadn't thought of that problem.

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1142 bytes --]