Skip to content
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

Migration guide for new assistant #768

Merged
merged 6 commits into from
May 6, 2019
Merged

Conversation

bethaitman
Copy link
Contributor

@bethaitman bethaitman commented Apr 29, 2019

Have not added release note yet.

I'd particularly appreciate:

  • suggestions for the start of the doc, explaining the good things about the new assistant
  • a thorough check of the tables, to make sure I've got the migration details correct

Copy link
Contributor

@cocreature cocreature left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

docs/source/support/new-assistant.rst Outdated Show resolved Hide resolved
docs/source/support/new-assistant.rst Outdated Show resolved Hide resolved
@ghost ghost force-pushed the migration-to-new-assistant branch 3 times, most recently from 0a014aa to dc7bb4e Compare May 6, 2019 07:00
@bethaitman
Copy link
Contributor Author

I've made my final changes: I now consider this done enough for a first go (in that, this is as good as it'll get without user feedback, so that's what we should look for next.).

@cocreature cocreature force-pushed the migration-to-new-assistant branch 3 times, most recently from c23d120 to dbea50f Compare May 6, 2019 13:56
@mergify mergify bot merged commit d77384b into master May 6, 2019
@mergify mergify bot deleted the migration-to-new-assistant branch May 6, 2019 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants