Making WordPress.org

Opened 3 years ago

Last modified 4 weeks ago

#5679 assigned enhancement

Fuzzies need to be rejected in the development and the stable versions

Reported by: carike's profile carike Owned by: spiraltee's profile spiraltee
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords: has-patch
Cc:

Description

Example:
https://translate.wordpress.org/projects/wp-plugins/wp-optimize/dev/af/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=642104&filters%5Btranslation_id%5D=29842680

Even though I already rejected this exact string for the stable version, I now need to go back and reject it for the development version.
This is something that leads to a tremendous amount of extra work for GTEs and the work has no benefit to the GTEs, or to the community at large, but we have to do it, otherwise the waiting / fuzzy filter is littered with old translations that makes it impossible to find new contributors. I.e. it leads to fatigue and burn-out.

And it makes me a very grumpy lion :)

Change History (6)

#1 @ocean90
3 years ago

  • Component changed from International Sites (Rosetta) to Translate Site & Plugins
  • Type changed from defect to enhancement

#2 @ocean90
2 years ago

#5992 was marked as a duplicate.

#3 @psmits1567
2 years ago

Not only when rejecting a fuzzy, but also if a suggestion is rejected and the same translation is present in dev!
Because sometimes the same translation is present in stable and dev unfortunately

#4 @Amieiro
18 months ago

  • Owner set to spiraltee
  • Status changed from new to assigned

This ticket was mentioned in PR #120 on WordPress/wordpress.org by trymebytes.


17 months ago
#5

  • Keywords has-patch added

Ticket - https://meta.trac.wordpress.org/ticket/5679

At the moment, translations are synced to both dev and stable versions only when it is approved on either versions. This implies that when a translation is approved and set to current in dev, the stable version is automatically updated with that approved translation but when a translation is rejected or set to fuzzy or changes requested on dev, the stable version is not updated and vice versa.

With this PR, when a translation is marked as fuzzy, rejected or changes requested on dev version, the same is applied/synced in the stable version and vice versa.

How to test

  1. Suggest a translation on the dev branch if there are no waiting strings for a project.
  2. As a PTE/GTE, set selected waiting translations to rejected, fuzzy or changes requested.
  3. The translation rejected on the dev branch should also be rejected on the stable branch.
  4. Repeat steps 1-3 starting with the stable branch in step 1.

#6 @timse201
4 weeks ago

Last edited 4 weeks ago by timse201 (previous) (diff)
Note: See TracTickets for help on using tickets.