I have moved all wicket-N.x branches for Wicket versions we no longer
support to archive/wicket-N.x. These branches are now also protected,
just as wicket-N.x branches, rel-branches and master/main.

I also crafted a wicket-11.x branch, and set master to release
wicket-12.x. I also changed the dependabot settings for 10.x and 11.x
to not update major versions of dependencies.

Before I step onto someone's old experiment, I have this list of
branches I want to remove from the wicket repository:

| Branch | Last commit | SHA |
| --- | --- | --- |
| jakarta-api | 2020-01-10 | 59b6a0554f |
| csp | 2020-02-12 | e5505cf6d5 |
| WICKET-6807_js_submitter_always_via_hidden_field | 2020-08-06 | 0c75de9606 |
| wicket-6831-w8 | 2020-10-01 | bed559fdf5 |
| WICKET-6847-onEndRequest-before-flush | 2020-11-11 | eac4e97c88 |
| WICKET-5768 | 2021-01-27 | 11dc8f94b9 |
| WICKET-6902-js-after-components | 2021-07-17 | 1f2064274c |
| WICKET-6908-detach-failure | 2021-07-26 | 05ab77655f |
| jmx-standardmbean-instead-proxy | 2021-08-21 | 7b3b938c06 |
| WICKET-6913-wicket-9.x | 2021-08-23 | 8287aa9f76 |
| WICKET-6981-session-attributes-not-set | 2022-05-24 | fbce20096c |
| wicket-6993-escape-attributes | 2022-08-16 | 25527239d8 |
| remove-queuing | 2023-02-08 | 5a73dd1f7e |
| reiern70/WICKET-7062 | 2023-06-21 | 00f91bfad7 |
| fix/WICKET-7065-filter-form-inline-js | 2023-07-28 | 9c7928fba2 |

These are all older than 2 years.

Anything worthy of keeping or nuke them out of existence?

Martijn

Reply via email to