On Mon, 17 Nov 2025 18:31:40 +0100
Daniel Kiper <[email protected]> wrote:

> On Tue, Nov 11, 2025 at 01:15:53AM -0600, Glenn Washburn wrote:
> > po files will now be tracked. This has the following benefits as listed
> > by Colin Watson:
> >
> >   * Build processes would no longer be vulnerable to an external server
> >     potentially going down for an extended period of time; they'd be
> >     stuck with outdated translations until the server was fixed or came
> >     up with a workaround, but that's better than nothing.
> >
> >   * It would be easier to manage branches of stable releases, rather than
> >     assuming that translations downloaded for master will match the POT
> >     files for a stable release.
> >
> >   * Tests would be able to pass from a clean git checkout without relying
> >     on an external server, improving QA reliability.
> >
> >   * It would be easier to make and test branches while offline.
> >
> >   * The translations shipped with a release tarball could be tagged in
> >     git so that it's easy to investigate bugs in them.
> >
> >   * Downstream distributors would be able to use git branches without
> >     having to fill in additional files.
> >
> > Signed-off-by: Glenn Washburn <[email protected]>
> 
> Reviewed-by: Daniel Kiper <[email protected]>

And just as a reminder, one of the steps before setting a release tag
should be to run linguas.sh or bootstrap (if the patch to move linguas
into bootstrap has been merged), perhaps as is already done when doing
your testing before the release. And then to commit the updated po
files before creating the release tag and distribution bundles.

Glenn

_______________________________________________
Grub-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to