BTW, we do have a git release branch for every release we made, e.g. the latest one is https://github.com/fastai/fastai/tree/release-1.0.46, so you can test your skills and evaluate how much work it takes by volunteering to be a branch manager. You can make any release branch production quality stable, by becoming its maintainer and backporting bug fixes from master to it.
Docs are still an issue, since they are already out of sync with 1.0.46 release and follow master, but just handling the code would be a good start and you can see whether this is doable for you. In the least-effort scenario docs just remain as they were at the moment of the branching, with just fixes applied if need be - a very minor effort actually. Just need to make a docs.fast.ai/br/1.0.46/ online version.
p.s. in case my communications come across as I’m trying to make it look difficult so that we won’t have to do it - quite on the contrary this needs to be done - I’m just showing that it is hard unsexy work. It’s like working in the QA dept, very unsexy, but no serious business can do well without QA. This is also why we need your help with our test suite, btw.