Hi Rafaella,
thanks for the additional informations.
I will create the feature list at Feature Freeze and will announce it.
When the list has to be updated until Code Freeze, I will announce this
in this mailing list too.
But to eliminate Bug reports for non-translated new features, I will add
some comments in the announcements and the list.
Regards,
Thorsten
[EMAIL PROTECTED] wrote:
Hi Thorsten,
the wiki at
http://wiki.services.openoffice.org/wiki/Feature_Freeze_Testing_204 it's
a great document and I am really looking forward to reading the 2.1 one.
Let me add a few comments:
I will announce this list after Code Freeze, because all general work on
the version should be finished. At 2.0.4 only one feature missed this
deadline - Online Update :-( -. So it is a good point to start testing
the new features.
Also the translation should integrated in L10N builds after the Code
Freeze.
No. Translation is integrated on October 26th. The Code Freeze date -
November 2nd - is the same date of l10n CWS builds availability. this
means that we start l10n testing same date as code freeze and that all
new feature and changes have been translated by the code freeze date. If
we get this list after code freeze, this information will be missed
a) during the translation work
b) most probably during TCM l0n testing
This means that L10N testing can also start for the features
after this date. Earlier testing of these new features will lead to
translation issues -> xyz not translated until now. But they are
translated but not integrated until the builds.
I don't want to start testing on builds which are not yet fully
localized I want to use this information during translation and as soon
as l10n CWS builds are available....
So all features should be integrated until Feature Freeze, but testing
(especially for L10N) can start after Code Freeze effectiv.
Why do you need a list of the new feature?
for translation and l10n testing
- for testing the translation in the builds ?
=> after Code freeze
no. I need this information by UI freeze.
- for translation the new feature ?
=> after Feature Freeze
yes.
(but the translation is done in a database, or I'm wrong?)
wrong. Files are extracted from the DB - if you refer to the languages
Sun/Globalization usually works on. For all other languages the N-L
communities extract the translatable content from the CVS.
Regards,
Rafaella
Regards,
Thorsten
[1] : http://wiki.services.openoffice.org/wiki/Feature_Freeze_Testing_204
[EMAIL PROTECTED] wrote:
Hi Thorsten,
Thorsten Ziehm wrote:
Hi,
additionally to this query, Joost wrote all included features in the
release notes of the Development Builds. And as at the last release
I will post a list of integrated features after Code Freeze.
Do you mean after the Code freeze of the 2.04 release?
But as I know out of the last releases it is difficult to say at
this point of of the next release, which features will be
integrated. Some of the planned features could be on target 2.x.
These issues can be also integrated, when specification and
implementation are ready until code freeze. And other features on
target 2.1 can be shifted, when they are over due dates.
According to the roadmap for 2.1
http://wiki.services.openoffice.org/wiki/OOoRelease205 UI freeze is
October 5th. Translation will start on October 12th. Are you saying
that we will only know on November 2nd which features have been
integrated? Cannot imagine that we get strings and help description
to translate for features that you don't know if they will be
integrated.... What am I misunderstanding here?
Thanks,
Rafaella
I do not know any 'must' feature for 2.1. So I cannot give you any
list.
Regards,
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
