19:56:28 RRSAgent has joined #aria-at 19:56:32 logging to https://www.w3.org/2023/11/30-aria-at-irc 19:56:32 RRSAgent, make logs Public 19:56:33 please title this meeting ("meeting: ..."), Matt_King 19:57:01 MEETING: ARIA and Assistive Technologies Community Group 19:57:09 CHAIR: Matt King 19:57:24 present+ 19:57:31 rrsagent, make minutes 19:57:33 I have made the request to generate https://www.w3.org/2023/11/30-aria-at-minutes.html Matt_King 19:59:24 jugglnmike has joined #aria-at 20:02:27 murray_moss has joined #aria-at 20:03:03 present+ jugglnmike 20:03:08 present+ 20:03:32 scribe+ jugglnmike 20:03:54 howard-e has joined #aria-at 20:04:00 present+ 20:04:08 Matt_King: I want to discuss the sequence of events which need to happen in order for testing to begin again 20:04:37 Topic: Resumption of testing 20:05:03 Matt_King: We want to get as many of the test plans as we can in the new format through "draft review" and into "candidate review" 20:05:06 Joe_Humbert has joined #aria-at 20:05:37 Matt_King: We want to prioritize "command button", alert, link, and radio group (prioritized in that order) 20:06:02 Matt_King: We can't run the tests, yet, but we're going to talk about the things that need to happen in order to get to the point where we can run the tests 20:06:14 present+ 20:06:23 Matt_King: As of this morning, the pull request which enables us to preview the new test plans in the ARIA-AT repo (not in the ARIA-AT app) is merged 20:06:40 Matt_King: ...so that means that we can work on the pull request for the refactored button, link, alert, and radio group 20:07:01 Matt_King: We can preview them using the preview feature in the pull request and the local preview 20:07:16 Matt_King: That part of the work is done 20:07:55 Matt_King: My question for howard-e is: I assume that we don't want to merge them into main until the "import" feature (aria-at app #838) is merged. Is it correct that it would be a problem if we tried to merge sooner than that? 20:08:10 howard-e: You will have to merge at least on in order to test on sandbox 20:08:55 howard-e: There's a pull request (#998) which has all updated test plans. We're planning to merge that to sandbox. Doing so will circumvent the need to push to the "main" branch directly 20:09:28 howard-e: But it will not cause a problem if we merge some of those to the main branch. The version in production would not be updated because it will fail to import the new v2 test plans 20:10:31 Matt_King: That means the pull requests we already have for those test plans--IsaDC should be able to preview them, now, and make any changes 20:10:38 present+ IsaDC 20:11:13 howard-e: Just to clarify: you will need to merge in the latest changes from "main" into the pull request branches 20:11:40 s/"main"/"master"/ 20:12:08 s/"main" branch/"master" branch/ 20:12:37 s/main until/the "master" branch until/ 20:12:56 s/main branch/"master" branch/ 20:14:13 present James_Scholes 20:14:32 James_Scholes: we can close the existing pull requests and open new versions that are based on the latest 20:15:08 Matt_King: I will handle the two that I'm already managing 20:15:24 James_Scholes: So we have six to make "version 2 ready" 20:15:35 Matt_King: Just tell me when they're ready for me to review 20:16:29 IsaDC: This probably won't be ready by end-of-day Friday 20:16:47 Matt_King: But it seems like we should be ready in time for next Wednesday's meeting of this group 20:17:08 James_Scholes: We will aim for that, but I can't guaruntee that they will all be in a merge-able state by them. 20:17:17 Matt_King: The only one with any complexity here is "radio group." 20:17:44 Matt_King: The manual changes are basically: references, assertion priorities, and then just making sure that there weren't any commands that were doing the same thing but were worded differently 20:18:01 Matt_King: I think the first four will only take 15 to 20 minutes 20:18:50 James_Scholes: Yup. I'm hopeful we can, but our other obligations together with the complexities of "radio group" could impact the delivery schedule 20:19:27 Matt_King: So, by Wednesday, we could have some plans in the "master" branch 20:19:41 Matt_King: The next question is: when will it be possible for community group members to run tests? 20:19:55 Matt_King: My understanding is that there are two pieces of work which need to be deployed to production 20:20:32 Matt_King: Those are the importer and the test runner. I think they're currently represented in one pull request. 20:20:34 howard-e: That's right 20:21:06 Matt_King: If I reviewed that by Monday (along with the other reviews you've requested), would it be possible to plan a deployment for Monday? 20:21:15 howard-e: That should be possible 20:21:43 Matt_King: That would mean that by Wednesday's meeting, we would have some plans for folks to begin running and reporting data 20:22:13 Matt_King: Then it's a matter of lining up people to run tests, which we could hopefully start Wednesday of next week 20:22:59 murray_moss: I may be able to run tests after Wednesday of next week. I'll be at next Wednesday's meeting 20:23:18 Matt_King: Cool! Then we'll be able to assign some Test Plans to you at that time 20:24:14 James_Scholes: I will have bandwidth by Thursday of next week, provided that we're able to complete those pull requests in the mean time 20:24:36 James_Scholes: we may also be able to find someone else at PAC to run the tests 20:35:40 jongund_ has joined #aria-at 21:04:38 Zakim, end the meeting 21:04:38 As of this point the attendees have been Matt_King, jugglnmike, murray_moss, howard-e, Joe_Humbert, IsaDC 21:04:40 RRSAgent, please draft minutes 21:04:41 I have made the request to generate https://www.w3.org/2023/11/30-aria-at-minutes.html Zakim 21:04:47 I am happy to have been of service, jugglnmike; please remember to excuse RRSAgent. Goodbye 21:04:48 Zakim has left #aria-at 21:04:49 rrsagent, leave 21:04:49 I see no action items