On 16/12/2006, at 1:31 PM, Tora wrote:
Charles-H.Schulz wrote:here is a very, very small and rough draft of the page. As Thomas suggested I put it on the wiki: http://wiki.services.openoffice.org/wiki/NLC/localizedQAGreat. It clearly states what we should do on our localized builds to distribute them to the local market.
Yes, I think it's very useful, as a start. :)
I am not sure that the following idea could be put in the same page or in the separated page. It is a position of the local test within the development process of OpenOffice.org. Have a look at schedulein the web page http://wiki.services.openoffice.org/wiki/ OOoRelease21 .
This release schedule was about the only pathway I could see, in this my first release. But unfortunately, it's not that clear.
==============================================================
* UI Freeze : October 5th 2006 (New !! all new strings need ...
* Feature_freeze : October 12th 2006 (New !! New features ...
* Translation update 2.1 start: October 12th
* Translation update 2.1 delivery: October 26th, 2006
* code_freeze: November 2nd
* l10n CWS builds available: November 2nd
* TCM l10n testing on CWS builds: November 2nd - 8th
* pre release candidate (en_US only): November 9th 2006
* Last_cws_integration for fixes: November 16th 2006
* release candidate for all languages: November 23th 2006
* release candidate 2 for all languages: December 1st 2006
* Product release: December 12th, 2006
==============================================================
In the list, the local test is positioned in the very end of the
process, from release candidate to product release.
In this schedule, testing is mentioned only once, and with a set period of only a few days.
We actually need a link from each release schedule to a specific QA schedule page. This page would also explain what TCM is (I didn't know when I read it), what is expected of l10n projects in QA, and what needs to be done.
Reading the original release schedule, you would get the impression that all testing had been done by the end of November 8th 2006.
In general, which is why I'm also CCing this to the Releases list and to Rafaella, I recommend that the release schedule, a central path for all of us, and especially for new releases, should act as an entry point for further information.
It can do this by including links to the references: _____
* UI Freeze : October 5th 2006 (New !! all new strings need ...
[UI Freeze] link to info on submitting new strings
* Feature_freeze : October 12th 2006 (New !! New features ...
[Feature Freeze] link to info on submitting new features
* Translation update 2.1 start: October 12th
* Translation update 2.1 delivery: October 26th, 2006
[delivery] link to info on how to submit your translation(s)
* code_freeze: November 2nd
[code freeze] link to info on implications of code freeze
* l10n CWS builds available: November 2nd
[CWS] link to info explaining what a CWS is [builds] link to info on how to get builds created [available] link to build mirrors
* TCM l10n testing on CWS builds: November 2nd - 8th
Add [QA] link to general QA pages at the beginning of this line [TCM] link to info on TCM[l10n testing] link to specific info on tests that must be run by l10n projects
* pre release candidate (en_US only): November 9th 2006
[pre-release] link to info on purpose of pre-release builds
* Last_cws_integration for fixes: November 16th 2006
[cws_integration] link to Pavel's slideshow on the OOo build process
* release candidate for all languages: November 23th 2006
[for all languages] link to the build mirrors
* release candidate 2 for all languages: December 1st 2006
[for all languages] link to the build mirrors [2] link to page of final checks for release
* Product release: December 12th, 2006
[release] link to release announcement and request for translations _____None of this makes the release schedule text any longer: it simply integrates hyperlinks into the text. The release schedule text was on a OOo wiki page.
Info of this type would have been a huge help to me in this my first release. I think it would help everybody in general, and newer people in particular.
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
