GIMP Translations for gimp-2-10 branch are being retired soon

Same as for the gimp-help module, we plan to retire the ability to translate the 2.10 branch for GIMP.

As I understand, there could be some opened workflows on the branch (I don’t know how to verify this) so in order not to waste anyone’s work, I’m following the best practice, as @jboerema, to announce the retirement from Damned Lies. :smile:

Please if you have any unfinished work on this branch, our advice is to finish it soon and move on to the master branch.

Notes:

  1. We don’t plan any new 2.10 release at this point. We are focusing on the 3.x series.
  2. We have a new accelerated planning now (to know more about our planning, read this link: Planning up to GIMP 3.2 (#13476) · Issues · GNOME / GIMP · GitLab), which means:
    1. We are currently in a stable “bug-fix” window. So now is the best time to push as many translations as possible, since we are not planning big textual changes (in a way, we are still somehow in a soft string freeze, even though GIMP 3 has been released). This bug-fix window will end by at least 1 more bug-fix version 3.0.4, though there may be some more. We will obviously warn with a thread here before every micro release.
    2. At some point (currently estimated around end of May), we will move to a Merge Window, which means we will start again to break things (new features, updated workflows, etc.), until we move to a third “Localization/Testing Window” where we will freeze features and localized text again.
  3. As a consequence of the above, right now, the master branch is still the only branch to work on. We will see if we decide to create a gimp-3-0 or gimp-3-2 branch eventually, but for now, it’s not planned. If this changes, we will make a thread here again.
1 Like

:information_source: Unfortunately, because of technical constraints, contrary to the gimp-help module, I am unable to provide a breakdown of ongoing workflows for gimp.

Coordinators

Please :pray: go to your team page, open the GIMP and Friends category (both for UI and docs), scroll down to Stable Branches, look for the lines that have anything in the Status column, check if there’s anything of value in these flows and deal with them. Up to you to decide which course of action is the best (commit with a cherry-pick to master, simply archive, maybe add a comment to the corresponding master flow to keep note of an insightful remark which was made in the old one, reupload the file to master to keep working on it and archive the old flow…). If you are unsure, don’t hesitate to ask here or on Matrix in #i18n:gnome.org.

2 Likes