The way I currently keep track of string changes in stable versions of D7 is pretty janky and imprecise. I tag as "String freeze" and mark as "Fixed" and hope that neither of those things changes by the time it's time to create release notes.

Now that we have API change nodes, it makes TOTAL sense to log these things there, imo.

So proposal would be to add "Translators" to the "Impacts:" field for string breakage.

What say you?

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Sounds like a good idea to me. It would need to be added as a field to the content type, and also added to the management view as a filter.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

And just a note that the Issue Summary page http://drupal.org/node/1155816 already has in the UI changes section a note that "changes to the user interface text" should be included, so I guess that doesn't need an update.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Do I need to do something with exporting this to a feature too?

drumm’s picture

drumm
he/him
Location NY, US
commented

Ideally, export and replace http://drupalcode.org/project/drupalorg.git/tree/refs/heads/6.x-3.x:/fea... in your local Git checkout, and upload the patch.

(I can do that part if I want to see something happen. But git diffs are less work for people doing deployments.)

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Assigned: Unassigned » webchick

Well I do enjoy giving you less work to do. :) Roger that.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Active » Closed (won't fix)

Actually we talked about this in IRC today. The best place for this alerting to happen would be on http://localize.drupal.org/, which is where the translation teams are actually looking. This would also expose a checkbox which is irrelevant on any D8 issue prior to whenever string freeze is called.

So "won't fixing" this in favour of a better solution on http://localize.drupal.org/.