[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: [RFC] short message "unfreeze" before KDE 3.5.1
From: Nicolas Goutte <nicolasg () snafu ! de>
Date: 2005-12-01 19:13:19
Message-ID: 200512012011.04302.nicolasg () snafu ! de
[Download RAW message or body]
As discussed a few weeks ago, there is a need to break (shortly) the message
freeze for fixing typos and other errors in user visible messages of KDE 3.5
before KDE 3.5.1.
This task has already started but before making it public to all KDE
developers, we should be perhaps discuss about the conditions.
* First, what can be changed?
We have talked about typos and other changes of existing messages until now.
If I remember well, there was a demand of adding some error messages. Should
this be allowed too?
What about adding other messages, potentially some that have more probability
of being seen by a user?
* Second, the time period
We need to decide about a date until such changes are allowed before freezing
again. I suppose that just a week is not enough, especially as developers has
not be forewarned. So I propose to allow changes until:
Monday 19 December 2005 (2005-12-19)
Time limit: 00:00 UTC (1 hour before Scripty will run).
(That would mean two full weeks, with time to prepare the announcement.)
* Third, technical details
I suppose that for the ease of everybody, as well for developers than for
translators, those changes should be done normally, triggering fuzzies.
I think that this is acceptable now as many translators will work on a
translation for KDE 3.5.1.
I suppose that a message should be sent to kde-commits-announce. As I suppose
that Stephan Kulow has not time to do such a text, it would perhaps be nice
if somebody could volunteer to write it. (If you do, please do not forget to
remind developers to add CCMAIL:kde-i18n-doc@kde.org in the commit message.)
(As for later "unfreeze" periods, I suppose that it should be done
transparently without fuzzies but with a searchable special comment (probably
with date). I have currently an idea how to implement it, but I have to
implement and to test it.)
(As for documentation, due to KDE's all-or-nothing policy, it is more
difficult to do something, so they are not part of this "unfreeze"
discussion.)
Have a nice day!
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic