This ticket will be used to have some kind of planning what goes into 1.2.0 release in terms of what are realistic goals. This release does not have any known breaking changes or dependent releases, so it should have a much quicker release cycle than 1.1.0.
If an issue will not directly be assigned to a known person with a context understanding of the issue, every issue needs to be verbosly written, so any maintainer or contributor can work on it or test it. I will add a column of complexity, to try to get new people who wants to contribute into the AI module, where you can pick easier tasks that doesn't require high context understanding if you are starting out.
If you are not a maintaner and want an issue added here, please ping us on Slack in #ai-contrib channel or tag it release blocker and version 1.2.x-dev.
Bug issues does not need to go here, but should be fixed according to priority and also be tagged backport to 1.1.x where needed.
Active
1.2
Discussion
@marcus_johansson
We can include Enable AI content suggestions only for chosen content types → and "Ask AI" button breaks UI when using streamed output in AI Explorers 🐛 "Ask AI" button breaks UI when using streamed output in AI Explorers Active , if it seems valid to you.
Thanks
Added the task - for bugs, they will be merged naturally and might also go to 1.1.x releases.