RFC 84: Public roadmap updates

[thibaudcolas]

Rendered

Follow-up to #79, defining more of the roadmap process (reviewing additions via RFCs), as well as proposing specific items for the next three releases.

[jacobtoppm]

I like the high level summary! The proposed features look good to me - but then I'm biased, quite a few of the ones I've been advocating for have made their way on. :P

[thibaudcolas]

Thanks @jacobtoppm :) Any thoughts about the review process? I tried to define it enough so there’s no guessing what constitutes "enough" review, but also not like something that has to be followed to the letter even for "small" additions to the roadmap.

[jacobtoppm]

@thibaudcolas I think it sounds like a sensible balance between the core team having some oversight and spending all our time reviewing tiny RFCs. And I'm glad you raised the point that bigger features that require their own RFCs/discussions don't need to fit in the RC window if they're split out - I think that would have been way too short!

[thibaudcolas]

👋 I’ve moved this RFC to Final Comment Period. We’re quite far ahead in the release cycle for the next version, I’d like our public roadmap to be up-to-date with the release’s contents at least 6 weeks ahead of the release date (half a release cycle).

[laymonage]

This looks good to me! Just a small comment on the permissions work as it's been postponed to 5.1.

[lb-]

No further comments from me. Thanks Thibaud and all

[thibaudcolas]

Thank you everyone for the feedback 🤘. I’ll merge this now and update the roadmap project accordingly.

[thibaudcolas]

wagtail.org/roadmap should now be fully up-to-date as per the additions here, and the roadmap README now details the review process as proposed in the RFC.