Will file subtasks for each as soon as it's out.
Thu, May 6
Wed, May 5
PR 498 is allowing CI to complete, but is just a temp work around. Bumping pytest to 6.2.4 *should* have fixed the issue (it did in channelmngt repo), but we were still getting failing on 3.10-dev.
https://github.com/MirahezeBots/MirahezeBots/pull/498 but I need to go.
Tue, May 4
Per conversation with @RhinosF1 on IRC, I'd recommend @MacFan4000 be nominated as, and confirmed subject to @RhinosF1's and the team's approval, the "designated survivor" with all powers to act for RhinosF1 where RhinosF1 has either:
- Formally designated himself on a leave of absence;
- Not been around for more than 72 hours without prior notice as to where he is; or,
- A simple majority of the team vote to temporarily invoke acting powers
I think any changes to MirahezeBot plugins should be able to be approved by any Operations-level team member (i.e., you, MacFan4000, Reception123, or Voidwalker). Likewise, changes to MirahezeBot trusted and admin level of access should require the approval of a majority of the team, at least three of which of which must be Operations-level team members.
Mon, May 3
3.7 will be EOL on October 4 with the support of 3.10
I slightly tweaked so we can drop 3.6 now with 3.8-dev.
The policy defines when its eligble for removal. Not when supoort must end.
I think we should stick with our 'previous+current+next' system. If Python has the volunteers to support extra versions, that's great for them but we don't. I recommend dropping 3.7 in October as planned.
Python changed support length which is why it's dodgy
Sat, May 1
Fri, Apr 30
Thu, Apr 29
Closing this as tasks have been created for all requests.