3.0 Action Plan: Gather items for the plan

RasaHQ / rasa

💬 Open source machine learning framework to automate text- and voice-based conversations: NLU, dialogue management, connect to Slack, Facebook, and more - Create chatbots and voice assistants

https://rasa.com/docs/rasa/

Apache License 2.0

18.95k stars 4.64k forks source link

3.0 Action Plan: Gather items for the plan #8766

Closed joejuzl closed 3 years ago

joejuzl commented 3 years ago

Description of Problem: As part of #8721 we need to collect the actual items for the plan. This will determine what will be released in 3.0

Creating the plan will be covered by #8763

Some notes from the brainstorm:

One documentation version for each major version
New architecture
Research owned features
Loading large datasets
Python 3.9 support
Maintenance e.g. dropping deprecations
Research specific maintenance

Blockers:

8763

Definition of Done:

[x] Until By date for 3.0 possibilities communicated to research (see here)
[x] Items that require a major release are identified
[x] Items sorted into likely must haves / nice to haves / can wait
[x] Issues for any necessary further spikes / investigations of must haves / nice to haves created
[x] Items added to the plan

wochinge commented 3 years ago

One engineer does preprocessing
Meeting with entire squad to finalize

wochinge commented 3 years ago

@TyDunn Updated the action plan. Please review and close issue if everything is alright. One note: How about creating an extra page property for the team which is responsible for a task (in addition to the current Assign field)?

m-vdb commented 3 years ago

@wochinge I'm not opposed to that, but how useful would that be?

TyDunn commented 3 years ago

@wochinge I reviewed. Everything looks good. I added one item for Slot Mappings and Forms improvements in case we decided to do it. If we don't, we can drop it. Feel free to close this issue once your conversation with Maxime is complete

wochinge commented 3 years ago

I'm not opposed to that, but how useful would that be?

Yeah, it might be rather a nice to have. I think it could be useful in case

the assignee is e.g. on vacation
to quickly see the distribution of projects on teams (e.g. to see if there is an unbalance)
to surface potential coordination effort (if a parent project has tasks from different teams)

@m-vdb

m-vdb commented 3 years ago

ok sounds good -- let's add it since it's low effort. Done!