Hah, okay, I guess something can't be in ContentTranslation and CX-analytics at the same time.

@Amire80, do I need to do anything special to get this triaged so it will get implemented soon? :)

It's probably an easy thing to do. It will be somewhere around here: https://phabricator.wikimedia.org/diffusion/ECTX/browse/master/api/ApiContentTranslationPublish.php$175

I haven't touched that code for a while, however, so I defer to @Nikerabbit for estimation.

@Nikerabbit, will we be able to do this soon? :)

The proposal looks good to me, I added the ticket to the quarter board (Language-2018-July-September).

One question is about whether it is possible (with a reasonable effort) to apply the tag retroactively. That is, to add the contenttranslation-v2 tag to those translations already created with version 2.

If it is not trivial, we can create a separate follow-up ticket to avoid increasing the scope of this one.
If it is hard, we can live with a few untagged CX2 translations.

Change 455916 had a related patch set uploaded (by Petar.petkovic; owner: Petar.petkovic):
[mediawiki/extensions/ContentTranslation@master] Introduce a distinct CX2 tag

https://gerrit.wikimedia.org/r/455916

In T201539#4529526, @Pginer-WMF wrote:

One question is about whether it is possible (with a reasonable effort) to apply the tag retroactively. That is, to add the contenttranslation-v2 tag to those translations already created with version 2.

If it is not trivial, we can create a separate follow-up ticket to avoid increasing the scope of this one.
If it is hard, we can live with a few untagged CX2 translations.

After discussion with the team, we plan to only tag the new translations for now.

Change 455916 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Introduce a distinct CX2 tag

https://gerrit.wikimedia.org/r/455916

In T201539#4554087, @Etonkovidova wrote:

@Petar.petkovic
The tag ContentTranslation2 tag is alwayas displayed along with ContentTranslation - was it intended?

Yes, that was an intention. To quote @Neil_P._Quinn_WMF:
For ease of analysis, I think we should set both tags on CX2 revisions: contenttranslation marking it as a CX edit generally, and contenttranslation-v2 making it as a version 2 edit specifically. That way, the contenttranslation tag will cover the first history, and we can then stop setting and querying the v2 tag once v1 has been fully replaced.

@Petar.petkovic, @Pginer-WMF I just queried the data, and so far I only see two edits with this tag in the production cluster: this one on the Spanish Wikipedia and this one on the Romanian Wikipedia.

Does that seem roughly right to you?

In T201539#4575742, @Neil_P._Quinn_WMF wrote:

@Petar.petkovic, @Pginer-WMF I just queried the data, and so far I only see two edits with this tag in the production cluster: this one on the Spanish Wikipedia and this one on the Romanian Wikipedia.

Does that seem roughly right to you?

Roughly yes. Access to version 2 is not very visible yet, so I don't expect many published articles. The work around T196435 can be useful to confirm data (you can check the graph here). That is based on the internal translation database, and for the recent period it shows 4-6 translation published. It would be good to check with @Amire80 if there may be some discrepancies to identify their cause (e.g., I assume that only translations published to the main namespace are counted, but we ma need to confirm).

We did a small outreach campaign in June asking 50 prolific users to publish an article with the new version and provide feedback, which may explain the spike in CX2 at the end of June. As we provide a switch for users to enable version 2 more easily (T194387) and do the corresponding announcements, we expect more people to use version 2 mor regularly.