From: mok@kde.ru
To: kde-rus@kde.ru
Subject: [kde-russian] Fwd: RFC: Semi-Freezing Docs
Date: Fri, 22 Feb 2002 05:40:53 +0300
Message-ID: <7930157944.20020222054053@bog.msu.ru> (raw)
Вот письмо, из которого ясно, что глубокий message freeze для
документации начинается со вторника, 26 февр. Для сообщений он уже
давно объявлен.
Все, что будет переведено до 7 марта, войдет в выпуск 3.0.
Однако фраза:
> Assuming tagging for the final RC is still scheduled for the 4th of
> March, and the Final for the 8th
говорит о том, что могут быть и изменения в сроках (понятно, в какую
сторону :).
This is a forwarded message
From: Lauri Watts <lauri@kde.org>
To: kde-i18n-doc@mail.kde.org
Date: Friday, February 22, 2002, 12:13:38 AM
Subject: RFC: Semi-Freezing Docs
===8<==============Original message text===============
Here's a proposal to cut down the number of inconsequential fuzzies (the
ones that correct errors in the english docs, but are not affecting the
translations, other than taking much time to mark done.)
Assuming tagging for the final RC is still scheduled for the 4th of
March, and the Final for the 8th:
Free-for-all until say, 10pm Monday evening UTC (25th February), and we
generate templates then for all the documentation.
After that, *only* factual content changes are committed, those that
change the meaning of the document, and therefore need translating.
Any other changes, spelling corrections and markup fixes, send a patch
(cvs diff -u) to kde-doc-english list, and I will collect them all,
and apply them on the day before tagging (at this point, that would be
the 7th of March). By that time, the languages that are to be released
will already be selected, and this last large set of commits will be
only those which don't require re-translation.
This should settle the documentation down greatly, I know the fuzzies
I've been creating must be an enormous task to keep up with, and I know
most of them are not affecting the actual translation at all.
FYI: Large documentation changes I know are coming include the FAQ (lots
of small changes) and kdeprint, which is getting another rewrite, but I
hope to have an initial version for translation by Monday.
Any objections, or exceptions please speak up now. If the above is
acceptable, I'll post it to the -devel lists, so hopefully those
developers who work on their documentation apart from the docs team
will take notice. Note, this doesn't apply to KOffice docs, which are
on a separate schedule.
Finally, this is similar to what we did for KDE 2.2.2, and it seemed to
work quite well. If it works out nicely again this time, I'll try to
get these dates added to the official release schedule for the next
time round.
Regards,
--
Lauri Watts
KDE Documentation Coordinator
===8<===========End of original message text===========
next reply other threads:[~2002-02-22 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 2:40 mok [this message]
2002-02-24 7:11 ` Albert R. Valiev
2002-02-24 17:42 ` [kde-russian] sborka kde-18n/ru mok
2002-02-25 2:10 ` Albert R. Valiev
2002-02-24 8:14 ` [kde-russian] Fwd: RFC: Semi-Freezing Docs А. Л. Клютченя
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7930157944.20020222054053@bog.msu.ru \
--to=mok@kde.ru \
--cc=kde-rus@kde.ru \
--cc=kde-russian@lists.kde.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
рассылка русскоязычной группы пользователей и разработчиков KDE
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/kde-russian/0 kde-russian/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 kde-russian kde-russian/ http://lore.altlinux.org/kde-russian \
kde-russian@lists.kde.ru
public-inbox-index kde-russian
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.kde-russian
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git