#18 Fedor 24 L10N test day planning
Closed: Fixed None Opened 6 years ago by pravins.

This ticket is to trac Fedora Localization test day and related activities.

[https://docs.google.com/document/d/17LU-PmtuirbGd7wfxUuKTz7X6fsv82PVPgZaDELi4js/ Planned dates in FAD]
2016-03-01 Alpha Release
2016-03-03 Software L10N QA Test day
2016-03-15 Software Translation Deadline
2016-03-21 Software I18N QA Test day

New proposed date
[https://lists.fedoraproject.org/archives/list/fltg@lists.fedoraproject.org/thread/O2CR62T4RRF25PSYPGSDH4KNNSHLR3IU/ 29th March (Tuesday)]

Please ignore the above dates to avoid confusion.

The current release schedule is: https://fedoraproject.org/wiki/Releases/24/Schedule.


Based on [https://lists.fedoraproject.org/archives/list/fltg@lists.fedoraproject.org/thread/O2CR62T4RRF25PSYPGSDH4KNNSHLR3IU/ mailing list] discussion 29th March has been selected as a Translation Test day.

Time to decide TODO list for successful Translation test day.

Updating as per meeting discussions.

Preparing test day Wiki. (Ani?)
Getting test-image for QA for testday (Ani?)
Writing article in community blog prior test day. (decause)
Proposing badges for test day. (decause) - This should start processing quick, since it takes time to get ready.

Please add missing steps if any.
* Tests creation, Testday app etc. and people responsible.

All tasks pertaining to Fedora24 L10n test day activities are tracked here :

From #480.

Test day page created: https://fedoraproject.org/wiki/Test_Day:2016-03-29_Translation_Test_Day
Fed Cal: https://apps.fedoraproject.org/calendar/QA/2016/3/29/#m3327

Discussions from todays meeting:
1. <jibecfed>: If we do vFAD from 21-29, is there any chance to get Translation available in Test image. More to follow up on #480.

Overall good number of member participated.

Noriko planning to prepare report for this test day.

Ani exported results for test day: https://fedoraproject.org/wiki/Test_Day:2016-03-29_Translation_Test_Day#Fedora_24_Test_Day_Report

In Short:
42 Applications, 11 Languages, 46 bugs reported, 15 participants.

Open Tasks: Bug Triaging.

Due to no contributor and not correct time, dropping plan for posting testing reports on community blog.

For Bug triaging. Reporting new ticket regarding trans-bug list and these bugs will get listed there.

Login to comment on this ticket.