#271 L10N and i18n Test Day
Closed: Fixed None Opened 10 years ago by aalam.

for localized and i18n testing, need two test days (including anaconda/installation) testing. Fedora 16 has test week. We can contiune with test week [https://fedorahosted.org/fedora-qa/ticket/222], After Software Translation Deadline (2012-03-13), it will be helpful for testing desktop.

Proposed Days:2012-03-22 or 2012-03-29

Some i18n Feaure in Fedora 17:
http://fedoraproject.org/wiki/Features/Inscript2_Keymaps

https://fedoraproject.org/wiki/I18N/Meetings/2011-12-22


Unfortunately I won't be available this time due to my day job, but I think it's a good idea to keep the Test Week in the same way we did for Fedora 16. Participation from volunteers was good and it worked pretty well.

Igor, if you can put together a basic Wiki page and link it here, I'll schedule a week.

Igor, do you think that the test week should be scheduled the week after translation freeze?

I'd rather have it scheduled a week before the translation freeze. That way translators would have enough time to fix whatever needs to be fixed before the freeze. That is what we did for Fedora 16 for instance.

2012-03-08 already booked by OpenStack. So either we need to choose 2012-03-01, which I think is not good as , or 2012-03-15 just after translation deadline. We need to do:

i18n/Translation installation (1st Day)
Translated Desktop Testing (2nd Day)
i18n Desktop Testing (3rd Day)

this can be completed in a week (3 days)

If the week of 2012-03-08 is particularly convenient for you, you could certainly run your event on Mon/Tue/Wed or Tue/Wed/Fri or something. We list the Thursdays to try and get a nice rhythm of events going, but there's no problem making exceptions for good reason.

Replying to [comment:6 adamwill]:

If the week of 2012-03-08 is particularly convenient for you, you could certainly run your event on Mon/Tue/Wed or Tue/Wed/Fri or something. We list the Thursdays to try and get a nice rhythm of events going, but there's no problem making exceptions for good reason.

It will be better if l10n Test day before Translation Deadline. We can do it on 2012-03-07 (Wednesday) if possible. i18n Test day we can use available slot of 2012-03-15. As anaconda builds regularly, language installation test day event can be later in April.

Software translation deadline is 2012-03-13. l10n test day must be arranged before this date, allowing last minutes fixes to be included. Please make l10n test day on 2012-03-07 (Wednesday).

Okay, you're in the schedule. If you could put your wiki page at https://fedoraproject.org/w/index.php?title=Test_Day:2012-03-07 I would appreciate it.

I just created 2012-03-07 Page. Next need to add 2012-03-15 Test Day for i18n.

For L10N Test day, a live image with latest translation is needed.
The reminder sent to devel-announcement asking fedora maintainers to pull, re-pack and push to koji by 2-Mar.
The ticket of rel-eng created asking for a live image compose specifically for this test on 5-Mar (https://fedorahosted.org/rel-eng/ticket/5106).
[[BR]]
Now I am wondering if any member of QA rather can compose a image without bothering rel-eng?

Replying to [comment:10 aalam]:

I just created 2012-03-07 Page. Next need to add 2012-03-15 Test Day for i18n.

hi jdulaney

as 2012-03-15 booked, can we get 2012-03-14 for i18n Test day. Other open slot (2012-04-26) will be too late otherwise.

Replying to [comment:7 aalam]:

Replying to [comment:6 adamwill]:

If the week of 2012-03-08 is particularly convenient for you, you could certainly run your event on Mon/Tue/Wed or Tue/Wed/Fri or something. We list the Thursdays to try and get a nice rhythm of events going, but there's no problem making exceptions for good reason.

It will be better if l10n Test day before Translation Deadline. We can do it on 2012-03-07 (Wednesday) if possible. i18n Test day we can use available slot of 2012-03-15. As anaconda builds regularly, language installation test day event can be later in April.

Thanks for offering of i18n test days. that would be nice if we can have one prior to the beta change deadline. so we will have a chance to update i18n packages if necessary.

Replying to [comment:11 noriko]:

I can build live images if needed. Actually, you probably could too, it's actually very simple to do. You basically just need a git checkout of spin-kickstarts:

http://git.fedorahosted.org/git/?p=spin-kickstarts.git

and the livecd-tools package installed. Then you run a command something like this:

livecd-creator -c /path/to/spin-kickstarts/fedora-live-desktop.ks -v -f my_awesome_live -t /home/adamw/local/live/tmp/ --cache=/home/adamw/local/live/cache/

-c is the kickstart to use, -v is verbose, -f is the filename and label to use for the resulting image, -t specifies the temporary directory and --cache specifies the cache directory (I think otherwise it uses /tmp and /var/something; I do this so the temp stuff can be re-used on subsequent attempts and the cache doesn't overflow my smaller / partition).

To do your customizations, you can take advantage of kickstart inclusion. Create a new kickstart file which includes the official kickstart you want to base your image on, and adds your customizations. So I have this kickstart file which just adds a couple of repos, for instance:


%include spin-kickstarts/fedora-livecd-desktop.ks

repo --name=side --baseurl=file:///home/adamw/local/repo2/$basearch [[BR]]
repo --name=bleed --baseurl=http://kojipkgs.fedoraproject.org/mash/bleed/$basearch


Or one which adds a package:


%include spin-kickstarts/fedora-livecd-desktop.ks

repo --name=side --baseurl=file:///home/adamw/local/repo/$basearch [[BR]]

repo --name=bleed --baseurl=http://kojipkgs.fedoraproject.org/mash/bleed/$basearch

%packages [[BR]]
rendercheck [[BR]]
%end


anyway, that's the basic idea.

BTW how do you take care of the packages being pushed for translation updates after reading the announcements? without the certain karmas, it takes 7 days to move it to the stable.

Ah, nevermind. 3 days for f17...

Replying to [comment:15 adamwill]:

I can build live images if needed. Actually, you probably could too, it's actually very simple to do. You basically just need a git checkout of spin-kickstarts:
[[BR]]
Thank you so much for your kind! [[BR]]
It would be much easier and faster to ask you or to be done by our test group newly formed next time. This time, the ticket has been created and owned by the member of rel-eng so I will wait for it.

Replying to [comment:5 aalam]:

2012-03-08 already booked by OpenStack. So either we need to choose 2012-03-01, which I think is not good as , or 2012-03-15 just after translation deadline. We need to do:

i18n/Translation installation (1st Day)

L10N and I18N testing successfully completed.

Next is Installation (L10N/I18N) testing.
Page is created [1].
Proposed date for installation testing is 2012-04-05.

[1] https://fedoraproject.org/wiki/Test_Day:2012-04-05_L10n_I18n_Installation

this can be completed in a week (3 days)

It's very close to PowerManagement Test Day (2012-04-04), but I think we can't propose anything much better than that. I see you already modified the schedule. It's settled then.

Replying to [comment:22 kparal]:

It's very close to PowerManagement Test Day (2012-04-04), but I think we can't propose anything much better than that. I see you already modified the schedule. It's settled then.

sorry for late addition of Test day, next time, we will take care.

Fedora 17 i18n/l10n Test Day Report:

https://fedoraproject.org/wiki/FLTG/Fedora17_Report

Task completed. Closing Ticket

Login to comment on this ticket.

Metadata