What steps will reproduce the problem?
1. Create an exploration on an Oppia instance with an old schema
2. Run the migration job
3. Go into your notifications list
What is the expected output? What do you see instead?
No new notification should be added due to the migration. However, the
migration bot does lead to a notification being shown.
There are two possible ways to address this problem:
1. Prohibit the migrations from showing up as a notification.
2. Change the message for migrations to be more clear. It may be useful for
exploration authors to be notified their exploration has been updated, in case
something goes wrong with it and they need to contact the Oppia development
team. However, the current migration message is for internal developer usage
and is too technical for exploration authors.
Original issue reported on code.google.com by bhenn...@google.com on 29 Jun 2015 at 9:07
Original issue reported on code.google.com by
bhenn...@google.comon 29 Jun 2015 at 9:07