-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Update "migrate from" code to match any updates to training data formats #6474
Comments
@akelad The @RasaHQ/production-engineers were asking if your team has bandwidth to take this on. Maybe it could be a joint effort? For example, someone on your team could handle investigate the changes to to other platforms and update the documentation, while someone on the production squad updates the converters |
@RasaHQ/cseteam thoughts? I'm not so sure about bandwidth, there's a lot of docs stuff going on still as well. |
I'm not so sure about bandwidth either tbh |
@TyDunn I think this is a @RasaHQ/loop-squad topic as it's related to the training data. |
@wochinge The loop squad has a lot going on right now to make Rasa X compatible. If the production squad has bandwidth, then I think we should pick it up |
We moved this to 2.1 as no squad has the bandwidth for it. Do you have strong objections @akelad ? I know it's not ideal but the only alternative would be to push the release. |
Ok, let's discuss these things on issues 👍 |
@RasaHQ/cseteam @RasaHQ/production-engineers @m-vdb I split the work between squads. CSE will investigate what we need to do update the convertors and docs, so that production squad can make the necessary updates to the convertors. Before we ship, we will need one of the two teams to update the docs |
@TyDunn should this issue be closed then since we have other issues? |
@akelad Let's keep this as an umbrella ticket that we close once all three sub-issues are complete |
There have been a few changes/updates to some of (or maybe all of) the platforms we offer migrations from:
For Rasa 2.0 these should be updated both to convert to the new yaml training data (unsure if that's already done), and also to read any new training data formats from these platforms.
Things that need to be done:
The text was updated successfully, but these errors were encountered: