[GRASS-dev] [release planning] 7.4.0

Maris Nartiss maris.gis at gmail.com
Thu Dec 21 01:24:53 PST 2017

If I understood correctly, the proposed workflow is to switch
Transifex to 7.4 branch and keep it there till 7.6 branch is created.
Sounds OK.

Here is a quick list of TODOs:
* provide a script to run before each stable release that pulls
translated messages from Transifex and replaces(!) PO files in SVN. It
is important to replace existing PO files with Tx version to prevent
generation of fuzzy entries in the final PO file;
* update documentation:
** How to release;
** locale/README;
** Wiki & web page;
* document how switching between branches should be done.

As for any team willing to translate only in SVN (that's me) – only
the pulling script will have to be modified to exclude language while
pulling translations from Transifex. That's really easy and I'll do
that as soon as the script is in place.


2017-12-20 22:13 GMT+02:00 Markus Neteler <neteler at osgeo.org>:
> On Wed, Dec 20, 2017 at 5:31 PM, Moritz Lennert
> <mlennert at club.worldonline.be> wrote:
> ...
>> I agree that we do not have to guarantee that the development version is
>> translated. IMHO, priority for translation should go to the stable,
> +1
>> or soon-to-be version which would mean that as soon as we create a release
>> branch, translations should be maintained for this release branch as long as
>> it is supported,
> +1
>> but any old release branch should be in strict bug-fix only
>> mode as soon as a new release is out, so message strings should not change
>> much.
>> Does that sound feasible ?
> This is what I also think. Yet the workflow isn't fully implemented
> yet. And Maris will appreciate to not lose his translations (how to do
> that?)...
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

More information about the grass-dev mailing list