[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Paul Gevers] bullseye and the release notes



Всем привет!

Неумолимо приближается выпуск bullseye, хорошо бы привести перевод
документации в порядок. В пересылаемом сообщении речь идёт об информации
о выпуске, но то же актуально и для руководства по установке, а также
для самой программы установки.

Если кто-то желает взяться, то сейчас самое время. Конечно, будут ещё
изменения в оригиналах документации, но позже будет проще доперевести
небольшие куски, чем за раз большой фрагмент.

Всего наилучшего,
Лев


-------------------- Start of forwarded message --------------------
From: Paul Gevers <elbrus@debian.org>
To: debian-l10n-english@lists.debian.org, debian-i18n@lists.debian.org,
 debian-doc@lists.debian.org
Cc: Debian release team <debian-release@lists.debian.org>
Subject: bullseye and the release notes
Date: Tue, 16 Mar 2021 21:55:26 +0100

Dear all,

As I hope you are all aware, we are in the final phase of the Debian 11
'bullseye' release. This means that we also want to get the release
notes [1] for bullseye into shape and translated.

Following the process that I proposed and used during the buster
release, I propose the following, if people have time to help out:

* l10n-english could do a review of the current text of all chapters.
That said, there haven't been much textual changes since the buster
release and the changes outside of issues.dbk have already been
reviewed. issues.dbk, and maybe whats-new.dbk, will keep receiving
updates during the releasing process, so the other files make more sense
to check first. I hope all members that want to contribute to the review
of proposed changes can also subscribe to merge request notifications in
the salsa interface [2], such that proposals that don't go via the bts
still get the proper attention. Bug reports in the bts are sent to
debian-doc@lists.debian.org, so consider subscribing to that list (or to
the release-notes pseudo package) if you want to help drafting or
reviewing incoming texts.

* Translation teams can start making sure translations are up-to-date, I
suggest starting with the about.dbk, installing.dbk, old-stuff.dbk,
moreinfo.dbk and release-notes.dbk files. issues.dbk, and maybe
whats-new.dbk, will receive more updates to existing texts (depending on
the answer to the review timing question in the previous paragraph)
resulting in possible unnecessary churn on fuzzy strings in just
translated items. I hope that after two weeks, in principle only new
text will be added.

I have seen updates to translations flowing in already, so I understand
at least some teams have direct access. I *guess* I can grant other
teams access if they request it. Since the archive is maintained in git
changes can be submitted with merge requests. Filing bug reports in the
bts against the release-notes package remain a supported option as well.

Please don't hesitate to ask if you have questions or remarks.

Let's get ready for the release.

Paul

[1] https://salsa.debian.org/ddp-team/release-notes
[2] on [1] hit drop-down menu next to the bell-sign and select what you
find appropriate

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

-------------------- End of forwarded message --------------------

Reply to: