-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC #106: Wagtail 6.5* and 6.6* roadmap updates #106
base: main
Are you sure you want to change the base?
Conversation
This is now ready for review :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like 6.5 is shaping up to be one for the benefit of headless users 👍
Couple of questions, no objections
|
||
The following Wagtail 6.4 roadmap items will be moved to Future: | ||
|
||
- [Autosave support refactorings with Telepath](https://github.com/wagtail/roadmap/issues/47) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: perhaps make explicit that Validation on publish
was identified during the 6.4 release cycle as something that takes precedence, which is why this was de-prioritized.
Question: out of curiosity, does this feature have sponsors? Do any roadmap items have sponsors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we have a sponsor for validation-on-publish, and in fact it's constraints on the funding (and when budgets can be spent) that have led to this being prioritised above the Telepath work, rather than any technical need for it to come first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, thanks for that context Matt 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the last release, drag'n'drop support was sponsored. In this upcoming release, in addition to validation on publish, we also have site settings permissions and some of the headless work (which bits exactly TBC)
Thank you for the feedback @Stormheg! There are a few elements of my answers I’ll want to move within the RFC contents but I’ll leave them as comments for now for others ’ benefit. I brought this to last week’s core team meeting briefly, and yesterday’s with a few more details, so marking this as "Final Comment Period". There’s lots of time for comments, I’ll be looking at updating our roadmap towards the second half of the month assuming we get enough feedback by then. |
I’ve updated the RFC based on feedback (thank you @Stormheg for the excellent questions!). Unfortunately I’ve also moved "Headless preview & userbar" from the Wagtail 6.5* release to "Future" as I didn’t realise we’re not clear yet when this can go ahead. Could still be 6.5* but it’s better for us to commit to fewer things that are more firm. More reviews/ feedback very welcome! |
Is it worth splitting the headless preview and headless userbar into two items? Maybe it's possible to merge the headless preview package into core as a somewhat easier first step. This may help set up some momentum for headless usage, even if it's one less dependency. |
View the RFC in HTML. Once reviewed with enough feedback and approved by the core team, those changes will go live on the Wagtail Roadmap.
6.5* and 6.6*: Provisional version numbers. See our Release schedule for more info.