Adding active devs and Yuri to check if anyone would like to add or change anything.

In D12531#254084, @yurchor wrote:

Maybe, it is worth to add the new version on top to release-overview.docbook, but we can do it anytime later.

Interesting. The doc contains the date of the release, which we don't know yet. Should we update it at the release time? However, this will bring a problem with translations, right? How to break this loop correctly?

In D12531#254089, @nmel wrote:

In D12531#254084, @yurchor wrote:

Maybe, it is worth to add the new version on top to release-overview.docbook, but we can do it anytime later.

Interesting. The doc contains the date of the release, which we don't know yet. Should we update it at the release time? However, this will bring a problem with translations, right? How to break this loop correctly?

Like in other apps. When we are ready we will enter into two weeks string freeze, announce to the translators that they should prepare and commit their translations by xx-xx-2018 and make the release on the announced day.

In D12531#254668, @martinkostolny wrote:

I agree with Yuri, about the release-overview addition. Although how do we notify translators? We announce it here?
kde-i18n-doc AT kde.org

Yes, I can do it, like with previous releases.

In D12531#254668, @martinkostolny wrote:

I agree with Yuri, about the release-overview addition.

Definitely. I'll send another review shortly. I'd like to keep this as a pure change log update.

I think we can now do the freeze

Let's do the freeze on Saturday. By the time D12524 must be merged, I'll merge this one and upcoming release-overview into master.

and propose release e.g. on Sunday, May the 13th?

Sounds good to me. I should be available on this day.