| 2 | | * empty the `p5-graveyard` port; we no longer need replacements for 5.8-5.14 |
| 3 | | * decide whether to keep or remove support for 5.20 (if we wait long enough with the ticket, 5.24 will be out anyway, so we may just as well remove 5.20 now :); on the other hand that should not mean removing all perl5 variants just because there will be a single perl left until introduction of 5.24 |
| 4 | | * close #48365 |
| 5 | | * ~~remove `perl5_16` ... `perl5_x` variants from `perl5`~~, r144338 |
| 6 | | * potentially collect a list of affected ports and warn maintainers (maybe try to make sure that we don't add a huge number of CC-ed users that will want to unsubscribe straight away while we still discuss what to do) |
| 7 | | * handle `subversion-perlbindings` |
| 8 | | * remove 5.16-5.x from `perl5.branches` from ports with variants |
| 9 | | * remove 5.16-5.x from all `p5-foo` modules |
| 10 | | * fill in the `p5-graveyard` port |
| 11 | | * (potential removal of `perl5.x` itself can wait) |
| | 2 | 1. empty the `p5-graveyard` port; we no longer need replacements for 5.8-5.14 |
| | 3 | 2. decide whether to keep or remove support for 5.20 (if we wait long enough with the ticket, 5.24 will be out anyway, so we may just as well remove 5.20 now :); on the other hand that should not mean removing all perl5 variants just because there will be a single perl left until introduction of 5.24 |
| | 4 | 3. close #48365 |
| | 5 | 4. ~~remove `perl5_16` ... `perl5_x` variants from `perl5`~~, r144338 |
| | 6 | 5. potentially collect a list of affected ports and warn maintainers (maybe try to make sure that we don't add a huge number of CC-ed users that will want to unsubscribe straight away while we still discuss what to do) |
| | 7 | 6. handle `subversion-perlbindings` |
| | 8 | 7. remove 5.16-5.x from `perl5.branches` from ports with variants |
| | 9 | 8. remove 5.16-5.x from all `p5-foo` modules |
| | 10 | 9. fill in the `p5-graveyard` port |
| | 11 | 10. (potential removal of `perl5.x` itself can wait) |
