mentioned in commit 709b0c65

@juliusv @teemo Could either of you review this? 😄

added 1 commit

• 709b0c65 - Add German translation for Cycle Analytics (!11161 (merged))

Compare with previous version

@DouweM Should this be ~"Pick into Stable"?

mentioned in commit 72b7fbbf

added 1 commit

• 72b7fbbf - Add German translation for Cycle Analytics (!11161 (merged))

Compare with previous version

/cc @rdavila

von Idee

von der Idee oder von einer Idee

This could be changed to the german word Ticket, but that only makes sense if this is being applied globally.

@haynes Technically "ticket" is not a German word either. 😉 I would leave "issue" here because it appears in docs and URLs. At least to me, "ticket" doesn't make it more clear than "issue".

I've seen it in quite a few german translations.
But I don't have a strong opinion about this. Let's leave it as Issue for now :)

In the text on line 29 we call the stage Produktion

Produktionsdeployment

Either use Produktiv or Produktion everywhere. Otherwise it's inconsistent.

@haynes You are right, I wasn't sure myself and it looks like I changed my mind during translation. 😟

I have heard "Produktivdeployment" a lot more often than "Produktionsdeployment". Also I thought that the feature is "Produktiv (deployt)" rather than "(in) Produktion". So I would choose "Produktiv" now.

Which one would you prefer?

both are possible with slight wording changes.
I think i like Produktiv a little bit better.

see comment above

Neues

That sounds so strange... but it looks like you are right. 😟

@winh can you give me a bit more context on that?
Ideally a screenshot of that site?

@haynes sure, you can see it here: https://gitlab.com/gitlab-org/gitlab-ce/cycle_analytics (Stage = Issue)

Maybe "Angelegt" is better than "Geöffnet" here?

yeah. Angelegt or Erstellt probably would be better here.

unless i missunderstood the english meaning this means something different.
past tense vs jobname...

Probably Zugehörige abgeschlossene Deployment jobs
would be more correct, but it's so long :(

@haynes I think that the job is finished ("abgeschlossen") is clear because we are only showing finished jobs on that page.

@winh alright :)

Comic
Commit

Damn autocorrection... 😞

Sobald Sie den ersten Commit pushen, werden dessen Daten hier erscheinen.

The time is what's important here. Not all the other data about the commit.

@haynes You are right, the focus is on the time but other data about the commit is shown as well. This is already inconsistent in the English text, for example: Begin creating issues to see data for this stage.

you're right. We should probably change the english wording to make it consistent :)

merge is used to often in these 2 sentences
reword it slightly or at least move the occurrences farther away from each other :)

replaced "mergen" with "abschließen"

Bearbeitung
Implementierung

@haynes Even in English, I think an issue cannot be implemented. It's rather implementation for an issue maybe? So what do you think about:

Zeit bis die Implementierung für ein Issue beginnt

?

fine by me 😄

lowercase and uppercase?
Is there really a difference here?

no, auto-correction again... 😞

@haynes Cycle Analytics = "Entwicklungszyklusanalyse"?

@winh I'd keep that as it is for now. Treat it as a name.
That way people can find the page in the docs 😉

mentioned in commit 32517657

added 1 commit

• 32517657 - Add German translation for Cycle Analytics (!11161 (merged))

Compare with previous version

mentioned in commit 073a5b87

@haynes If you have some time, could you take another look? 😃

added 1 commit

• 073a5b87 - Add German translation for Cycle Analytics (!11161 (merged))

Compare with previous version

resolved all discussions

@winh I didn't see any more Issues. Looks good to me 👍

@haynes Thank you very much for taking the time to review this! 😃

added ~149423 label

assigned to @DouweM

approved this merge request

unmarked as a Work In Progress

merged

mentioned in commit 1e4e0b27

mentioned in commit d876ba48

mentioned in commit dd1ee29d

mentioned in issue #32508 (closed)

@winniehell @haynes @DouweM

Given that:

• This is a Deliverable, not a bug or regression
• We have just 3 working days before the 22nd
• (edit) We have 100 MRs to pick for rc5

Does this absolutely have to go into 9.2?

@timothyandrew If it does not go into 9.2, I think we should remove it from the release post and disable the option to switch to German in user preferences. Being able to switch to German but not seeing any German seems weird to me.

• This is a Deliverable, not a bug or regression

@timothyandrew I'd say the deliverable is internationalization (which is already in 9.2). This one fixes the bug of German translation not being present. 😉

mentioned in merge request gitlab-com/www-gitlab-com!5551 (merged)

@timothyandrew Do you expect this to create merge conflicts? It seems to me like one of the easier MRs to pick, and as @winh points out, if we don't pick it, we'll have to pick another MR to remove the "German" option from the interface.

@DouweM: No, I'm just trying to avoid non-regression issues in the RCs, as per https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md#after-the-7th.

@stanhu: I'll leave this to you to sign-off on.

assigned to @stanhu

@timothyandrew Let's go ahead here.

@kushalpandya: Could you please pick this into 9-2-stable for 9.2.0-rc7?

Picked into 9-2-stable, will go into 9.2.0-rc7.

removed ~149423 label

mentioned in commit 9f968cbe

@timothyandrew Thank you! 👍

mentioned in merge request !13756 (closed)