Re: [bug-gettext] gettext maintenance

[Daiki Ueno]

Hi Bruno,

Bruno Haible <address@hidden> writes:

Good to hear from you.  Maybe I'm not so qualified to maintain such an
important software but let me try.

> I think Stefano's patch
> http://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=58ee4b61ff75d16ebbd3a9824fc228123eecb706
> merits a NEWS entry, because Autoconf 2.59 is still often used, I think.
> Something like this:
>
> * The autoconf macros installed by 'gettextize' now require Autoconf
>   version 2.60 or newer.

Sure.  Thanks for the entry.

> I have been receiving PO files from translators, by mail, over time.
> OK to commit them?

Sure.

> In which branches? Only 0.18.2 branch or both?

master would be better.  I meant 0.18.2 branch temporary use for this
release only and I'll rebase it against master (though non-FF commits
are not allowed on git.sv.gnu.org).

> What is your branch policy, btw.? Are merge commits allowed (like in
> Automake git)? Or forbidden (like in coreutils git and gnulib git)?

Not yet decided, but I think it would be good to follow the existing
policy (if any).

> What is your ChangeLog policy? I see some of your commits have ChangeLog
> entries, some don't. You decide, I'm only asking.

Same here.  I'd like to follow your policy.  I looked at the commits
around 0.18.1 release and just mimicked them.

> http://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=a094a1a0a1b366927189d068c64c00f46ac186dd
> In gettext-runtime/intl/lock.c you replaced the LGPL copyright header
> with a GPL copyright header. This is not good, because it causes libintl.so
> to become a GPL library, with the consequence that proprietary programs
> cannot link against it any more.

Right, thanks for pointing this out.

> You have seen the file Admin/release-steps? I'm asking because I see
> no changes to gettext-tools/misc/autopoint.in.

Yes, it seems that I forgot to do the steps after "make distcheck" in
Admin/release-steps.

Regards,
-- 
Daiki Ueno