I'm going to ignore the first paragraph and respectfully suggest amending your approach:
- Do not publish stable releases and label them as suited for a specific version if they have no (as in NONE, ZERO, NULL) functionality.
- This issue is a child issue of #3476179 🐛 Symfony\Component\Routing\Exception\RouteNotFoundException Active and should have been treated and labeled as such.
- Machine testing is always inferior to user feedback -- as in " That settings form is one of the very few things that is tested in this module, and the tests show no errors accessing that page. 🐛 Symfony\Component\Routing\Exception\RouteNotFoundException Active "
- Do not mark issues as
Needs review
if you do not wish/require user input. Leave them asactive
. - Always encourage and enable testing by users.
Interesting. Especially if one would add project/role_expire → . This would create a diverse low-level subscription system. Also, I suppose it would make sense to port the voucher sub-module for this to work and have users not loose access to existing accounts.
There is no way to run/test this on D11 before #3476179 🐛 Symfony\Component\Routing\Exception\RouteNotFoundException Active is fixed and committed.
Works for me.
neurer → created an issue.
MR16 works for me.
Can confirm MR !94 fixes this. Please commit.