05:30:18 #startmeeting i18n 05:30:18 Meeting started Tue Mar 12 05:30:18 2019 UTC. 05:30:18 This meeting is logged and archived in a public location. 05:30:18 The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:30:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:30:18 The meeting name has been set to 'i18n' 05:30:18 #meetingname i18n 05:30:18 The meeting name has been set to 'i18n' 05:30:18 #topic agenda and roll call 05:30:18 #link https://fedoraproject.org/wiki/I18N/Meetings/2019-03-12 05:30:27 hi 05:30:28 hi 05:30:37 hi 05:31:12 #chair tagoh pwu juhp 05:31:12 Current chairs: juhp paragan pwu tagoh 05:31:57 hi 05:32:01 let's wait a minute to see if more people can join 05:33:15 @chair vishal_vvr 05:33:19 let's start 05:33:34 #topic Upcoming schedule 05:33:34 #info 2019-03-26 Beta Release (Preferred Target) 05:33:34 #info 2019-04-02 Beta Release (Target #1) 05:33:47 we are currently in Beta freeze 05:34:07 Bodhi is already activated for pushing updates to F30 05:34:36 There is no successful compose for F30 since last 11 days now 05:35:16 Bit worrying for our testday 05:35:51 but we do have image generated for F30 SilverBlue https://kojipkgs.fedoraproject.org/compose/branched/Fedora-30-20190312.n.0/compose/Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-30-20190312.n.0.iso 05:35:57 not sure if its working 05:36:16 aha 05:36:42 I do see Workstation iso https://kojipkgs.fedoraproject.org/compose/branched/Fedora-30-20190311.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-30-20190311.n.0.iso 05:36:54 but still not sure if its working 05:37:25 so koji composes have iso images, we can take the recent one and test it 05:38:07 cool 05:38:30 Wonder why they are not getting pushed then - didn't read the releng meeting log :) 05:38:49 Other arches are blocked? 05:39:03 maybe we want all the arches also built images 05:39:38 at least we have something to test with ;-) 05:40:24 also, FESCo approved F31 schedule 05:40:34 https://fedoraproject.org/wiki/Releases/31/Schedule 05:41:39 is there anything to discuss for any issues related to F30 Schedule? 05:41:56 If not then we can move to next topic 05:43:25 we have Fedora 30 i18n test day next week Tue 19. We will discuss about it in our ticket discussions 05:43:29 moving on 05:43:47 #topic No assignee issues 05:43:47 #info #105: Fedora 28 Bug triaging (pnemade) 05:43:47 #link https://pagure.io/i18n/issue/105 05:44:39 This one is picked as first ticket because QE people have planned bug triaging event 05:44:47 it will be on 25th March 05:44:55 #info https://fedoraproject.org/wiki/QA/F28_I18N_Bug_Triage 05:45:42 so let's work with them and try to triage, fix, close the F28 bugs 05:45:53 Can we change the table column label from "Triage by" to say "Triager" or something 05:46:09 ugh from "Triaged by" 05:46:33 We want to assign people before not after triaging I suppose... 05:47:09 Though dunno how to show completed - so I think we need one more column for that? 05:47:11 I think its their internal work division like who is going to work/triage on bugs 05:47:15 bbarve: ? 05:47:31 I see 05:47:37 their/our? 05:47:52 I think their 05:48:24 hmm language 05:49:05 so the team will divide bugs into members and they work with devel people 05:49:18 So we don't work on it? 05:49:49 no I guess as its their own activity 05:49:53 Alright 05:50:11 maybe I am wrong in understanding their activity here but above is what I think 05:50:14 hmm 05:51:16 okay 05:51:26 let's move 05:52:17 #info #106: Fedora 30 i18n test day (pnemade) 05:52:17 #link https://pagure.io/i18n/issue/106 05:52:37 so Fedora 30 i18n test day is coming next week 05:52:43 19th March Tuesday 05:52:57 we have all the required things set up now 05:53:13 Test day page => http://fedoraproject.org/wiki/Test_Day:2019-03-19_I18N_Test_Day 05:53:23 Results page => http://testdays.fedorainfracloud.org/events/58 05:53:54 Request all to join on this day or maybe before or after that day to provide your test results 05:54:23 paragan +1 05:54:37 Yes 05:55:10 thanks 05:55:47 let's move to next ticket 05:56:40 #info #108: add Fedora CI tests to our important packages (petersen) 05:56:40 #link https://pagure.io/i18n/issue/108 05:57:46 I think we all are working on writing tests for our packages and there is not much to provide update here 05:58:25 What packages do we have in the pipeline? 05:59:02 or what tests? 05:59:20 I only tried one package to test if it provides metainfo file 06:00:30 maybe all team members can check which 1-2 packages they are maintaining is important for Fedora and start working on writing tests. 06:00:45 Yes 06:02:14 not much from me to discuss here 06:03:01 Do we have any deadline for this? 06:04:12 if needed we can set deadline for our team 06:04:39 I am more concerned about getting started really at this point 06:06:29 need more information you mean? 06:07:07 No, that we actually start to add tests 06:07:28 Well it will good to have tests for our packages by F30 GA 06:07:39 not all packages like said before 06:07:56 I suppose this is more for f31 devel but that we should have some tests in place soon 06:08:04 right 06:08:10 yes 06:08:24 https://fedoraproject.org/wiki/Changes/GatingRawhideSinglePackageUpdates 06:10:14 #topic Open Floor 06:10:22 anything to discuss here? 06:10:23 Should we all try to have one or more tests in place by the end of this month? 06:11:02 sounds good to me. 06:11:05 #chair 06:11:05 Current chairs: juhp paragan pwu tagoh 06:11:58 Looks good to me as well 06:12:48 updating ticket with above decision 06:12:57 does it need to be reviewed by someone after that? 06:14:13 if CI run is successful then I guess you have worked fine in writing tests. 06:14:32 It wouldn't hurt to have review 06:15:28 We don't have any requirements for testing so far. so just wonder if added testing is sufficient or not. 06:15:33 yes. People who are ready to push or already pushed can contact other members of team or even send an email on i18n list for review of your tests. 06:15:43 anyway, will update the ticket once I've done some 06:16:58 great 06:17:10 That's what i meant by getting started :) 06:18:33 anything more to discuss? 06:19:50 Closing meeting in 2 minutes 06:20:02 paragan: sure, i gone through the logs. Looks good to me. 06:20:22 Ok 06:21:28 Thanks all who came to this meeting :) 06:21:40 #endmeeting