)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e2860d8a1bc0a2e0061bc2f15342d5851f83df26","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"79f39634_0037efd6","updated":"2023-07-10 17:00:51.000000000","message":"I think I\u0027m missing the point of this resolution that just points to another resolution...?","commit_id":"d8f4cb1bd5c53210649d0ee279f3750cc2167657"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"32c973844fabd15471e72e5111ac8d5dfd505b76","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"08382e3f_26b139eb","in_reply_to":"79f39634_0037efd6","updated":"2023-07-10 19:21:00.000000000","message":"The other resolution, as written, only applies the new policy starting with stable/yoga, which is schedule to transition to EM in November. It doesn\u0027t attempt to affect branches R through X which are currently under EM.\n\nWhat to do with R-X I decided to split into a separate pair of resolutions.\n\n- (This one) Applying the requirements and opt-in process to current EM branches.\n- Grandfathering current EM branches and phasing them out into the new policy on a schedule.","commit_id":"d8f4cb1bd5c53210649d0ee279f3750cc2167657"}]}