Open fstrr opened 1 month ago
fstrr
commented
1 month ago @patrickhlauke Hey. There are 31 branches with your name on them. We decided last week that, in about a month, we're going to delete branches that are more than six months old. Could you go through your branches and delete what you don't want and add the ones that still need attention to the project board? Thanks.
patrickhlauke
commented
1 month ago i've looked at some of the closed PRs this week (while at side of the pool), and i think i spotted quite a few that now are closed because, in essence, the WG stalled on actually doing anything with them (sometimes even after eeaching apparent consensus, but then never merging). so i'd suggest having a bit of a closer look at hanging PRs that were closed, as they also then removed/closed issues that were indeed still valid concerns, just never got anywhere due to WG apathy/inertiaOn 28 May 2024, at 22:14, Francis Storr @.***> wrote: @patrickhlauke Hey. There are 31 branches with your name on them. We decided last week that, in about a month, we're going to delete branches that are more than six months old. Could you go through your branches and delete what you don't want and add them to the backlog board if they still need working on?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
fstrr
commented
1 month ago I have stated to delete WCAG 2.2 related branches that have a last-updated date that's before the date 2.2 became a recommendation. I'm working on the (maybe risky) assumption that that content would have made it into 2.2, so is fair game.
I'll pause on deleting any more until people have hopefully had a chance to look through some of them.
This continues the #3602 issue. This repo has roughly 250 branches, many of which don't have an associated pull request, or contain edits that have since happened elsewhere. This issue can be used to track these branches as they get updated, merged, or deleted.