Hi QA team
I am Noriko Mizumoto, coming from Fedora Localization Project. As we are in scheduling period, I'd like to propose new QA test to be created. Here is the detail.
I am quite new to QA activity, so it would be highly appreciated for your guidance.
[Introduction] For software translations, FLP translators work on PO file so they never know where particular string to be appeared in UI. The Build release packages for review allows translators to review their work in UI with the aspect of QA and to give a chance for correction. This event have been proposed by FLSCo and approved by FESCo [1].
[Test Strategy] This is the course of events order which can be found in the schedule [2]. 1) Software String Freeze (*Request f-dev-announcement for Build F13 pkgs with latest translation for L10n Review) 2) Software Translation Period (POT to PO) 3) Build F-13 collection packages for all language translators 4) Review and correct software translation in built UI 5) Software: Translation Deadline (PO Files complete) 6) Software: Start Rebuild all translated packages 7) Software: Rebuild all translated packages 8) Beta Freeze
At 3), all F13 packages will be built with latest translation by packagers. Then at the end of 3), Live Image needs to be crated for QA.
[Test Priority] n/a
[Scope] All components (packages) under F13 release [3].
[Test Pass/Fail Criteria] The test will be completed at the deadline date. See, 5) Software: Translation Deadline (PO Files complete)
7 Test Deliverables * High quality of translation * Bugs will be filed against package(s) which shows problem in translation [4].
[Test Cases] "Instruction" for consistent test to be created and posted.
[Test Environment] n/a
[Responsibilities] Packagers: Build packages with latest translation Translators: QA test for translation quality QA: Create Live image
[Schedule] See test strategy.
[Risks] Package not built according to the schedule by packagers. If this happens, that package will not display latest translation in UI making unable to review. To prevent this, the request (shown with bracket in the above) will be sent to f-devel-announce before 3) Build F-13 collection packages for all language translators.
[Reviewers] ?
[References] [1]:https://fedorahosted.org/fesco/ticket/243 [2]:http://poelstra.fedorapeople.org/schedules/f-13/f-13-all-tasks.html [3]:https://translate.fedoraproject.org/languages/nl/collection/fedora/fedora-13... [4]:https://fedoraproject.org/wiki/L10N/UpdatePot
Thanks noriko
On Wed, 2009-12-23 at 11:00 +1000, Noriko Mizumoto wrote:
Hi QA team
I am Noriko Mizumoto, coming from Fedora Localization Project. As we are in scheduling period, I'd like to propose new QA test to be created. Here is the detail.
Hi :)
I think we'd be happy to help with this however we can, but it seems like something that obviously depends on linguistic ability! We can contribute any of us in QA who speak languages other than English, perhaps.
For building images to test - in fact, live images are generated automatically, nightly, available at:
http://alt.fedoraproject.org/pub/alt/nightly-composes/
would this be to your requirements?
Thanks for all your work.
Adam Williamson さんは書きました:
On Wed, 2009-12-23 at 11:00 +1000, Noriko Mizumoto wrote:
Hi QA team
I am Noriko Mizumoto, coming from Fedora Localization Project. As we are in scheduling period, I'd like to propose new QA test to be created. Here is the detail.
Hi :)
I think we'd be happy to help with this however we can, but it seems like something that obviously depends on linguistic ability! We can contribute any of us in QA who speak languages other than English, perhaps.
Great, thank you!
For building images to test - in fact, live images are generated automatically, nightly, available at:
http://alt.fedoraproject.org/pub/alt/nightly-composes/
would this be to your requirements?
OH, this sounds awesome :-) Let me just double check, this image does contain all latest Fedora 13 packages built at that time, right? [1]
I am a bit of afraid if nightly build overrides next night build. For F13, in this case, I like to have "nightly-composes of 5-Mar-2010" image available between 5th and 16th of March. This allows translators to have QA test with exact one same image and file a bug if needed.
When we file a bug, Version-Release should be "nightly-composes of 5-Mar-2009". Is this sufficient for the packager to look in and fix if needed? e.g. [2]
Does this image also contain python-nss? This is to perform liveinst. [3]
Thank you and Happy New Year to all.
[1]:https://translate.fedoraproject.org/languages/nl/collection/fedora/fedora-13... [2]:https://bugzilla.redhat.com/show_bug.cgi?id=525033 [3]:https://bugzilla.redhat.com/show_bug.cgi?id=525022
noriko
On Mon, 2010-01-04 at 10:24 +1000, Noriko Mizumoto wrote:
I am Noriko Mizumoto, coming from Fedora Localization Project. As we are in scheduling period, I'd like to propose new QA test to be created. Here is the detail.
Hi :)
I think we'd be happy to help with this however we can, but it seems like something that obviously depends on linguistic ability! We can contribute any of us in QA who speak languages other than English, perhaps.
Great, thank you!
So, anyone on the list who is proficient in a language other than English - please do help out Noriko :)
For building images to test - in fact, live images are generated automatically, nightly, available at:
http://alt.fedoraproject.org/pub/alt/nightly-composes/
would this be to your requirements?
OH, this sounds awesome :-) Let me just double check, this image does contain all latest Fedora 13 packages built at that time, right? [1]
Yes, that's what it's intended for.
I am a bit of afraid if nightly build overrides next night build. For F13, in this case, I like to have "nightly-composes of 5-Mar-2010" image available between 5th and 16th of March. This allows translators to have QA test with exact one same image and file a bug if needed.
We don't typically do this, but I'm sure we could make arrangements to keep an image available for a given time. I think we wind up having a fairly-recent image available for one reason or another through most of the process anyway; I'll CC Jesse, who can explain in more detail. There's usually a recent snapshot or test compose or pre-release or _something_ available at any given point, right Jesse?
When we file a bug, Version-Release should be "nightly-composes of 5-Mar-2009". Is this sufficient for the packager to look in and fix if needed? e.g. [2]
Well, this isn't an option. You just set the release to Rawhide. You can mention the nightly image date and the specific package version in the bug report if you like. Generally packagers will ask if they need anything else.
Does this image also contain python-nss? This is to perform liveinst. [3]
This I don't know off the top of my head. You could download the latest nightly and test. If it's not, we can look at fixing that. Frankly the closing of the bug report seems a little odd to me; if anaconda needs python-nss to run, it should depend on it, I would think. We shouldn't have to add it to the live image manually. Unless there's some specific reason not to put it in the dependencies.
Thank you and Happy New Year to all.
noriko
Em Seg, 2010-01-04 às 12:20 +0000, Adam Williamson escreveu:
I think we'd be happy to help with this however we can, but it seems like something that obviously depends on linguistic ability! We can contribute any of us in QA who speak languages other than English, perhaps.
Great, thank you!
So, anyone on the list who is proficient in a language other than English - please do help out Noriko :)
I'm new here, but I'm sure I can help with this too. I can maintain contact with the Brazilian Portuguese and the European Portuguese translation teams, and also the Spanish team via Fedora LATAM.
Anyway, when I subscribed this list a few days ago, my intention was to help the i18n QA in a broader way. In short, I mean to avoid, report and correct i18n string bugs so they don't perturb the L10N teams from doing their job. Since this thread is already ongoing I'll be glad to improve this idea.
Does this image also contain python-nss? This is to perform liveinst. [3]
This I don't know off the top of my head. You could download the latest nightly and test. If it's not, we can look at fixing that. Frankly the closing of the bug report seems a little odd to me; if anaconda needs python-nss to run, it should depend on it, I would think. We shouldn't have to add it to the live image manually. Unless there's some specific reason not to put it in the dependencies.
From the experience I have on spin SIG the liveinst tool works with no
problems on images based on default kickstart files such -base and -desktop ones, so this should not be a problem, unless there is a new bug I'm not aware of.
Regards, Igor Pires Soares
Igor Pires Soares さんは書きました:
Em Seg, 2010-01-04 às 12:20 +0000, Adam Williamson escreveu:
I think we'd be happy to help with this however we can, but it seems like something that obviously depends on linguistic ability! We can contribute any of us in QA who speak languages other than English, perhaps.
Great, thank you!
So, anyone on the list who is proficient in a language other than English - please do help out Noriko :)
I'm new here, but I'm sure I can help with this too. I can maintain contact with the Brazilian Portuguese and the European Portuguese translation teams, and also the Spanish team via Fedora LATAM.
Anyway, when I subscribed this list a few days ago, my intention was to help the i18n QA in a broader way. In short, I mean to avoid, report and correct i18n string bugs so they don't perturb the L10N teams from doing their job. Since this thread is already ongoing I'll be glad to improve this idea.
Thank you for raising your hand!! As posted previous mail, I will make a post once ready to f-trans-l and f-test-list both.
This QA test is for L10N, so it is different from the one for i18n. And I am sure that i18n team do understand what we are looking at.
noriko
From the experience I have on spin SIG the liveinst tool works with no
problems on images based on default kickstart files such -base and -desktop ones, so this should not be a problem, unless there is a new bug I'm not aware of.
Cool, thanks! I also tried F12 live image yesterday, and it is working. So it should be no problem. Thank you!
Regards, Igor Pires Soares
On Mon, 2010-01-04 at 12:20 +0000, Adam Williamson wrote:
We don't typically do this, but I'm sure we could make arrangements to keep an image available for a given time. I think we wind up having a fairly-recent image available for one reason or another through most of the process anyway; I'll CC Jesse, who can explain in more detail. There's usually a recent snapshot or test compose or pre-release or _something_ available at any given point, right Jesse?
The only time there wouldn't be would be prior to the feature freeze and source control branch.