-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Remove muon / Brave (old) from importer #7403
Labels
feature/importer
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
Milestone
Comments
Thanks for filing this @LaurenWags ! |
rebron
added
the
priority/P3
The next thing for us to work on. It'll ride the trains.
label
Dec 17, 2019
32 tasks
Verified passed with
Verification passed on
Verification passed on
|
rebron
changed the title
remove muon / Brave (old) from importer
Remove muon / Brave (old) from importer
Apr 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature/importer
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
Description
Per internal discussions, we decided to remove muon from the list of browsers to import from. It has been over a year since we did the migration from muon. Additionally, it is confusing to some users as they think they can import from other channels.
Test plan / Steps to Reproduce
Actual result:
Brave (old) is in the list to import from.
Expected result:
Brave (old) should not be in the list.
Reproduces how often:
easily
Brave version (brave://version info)
all
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
at least one internal suggestion for this occurred here, but there were other discussions as well.
https://bravesoftware.slack.com/archives/C20HMJ62H/p1575914247322000
cc @bsclifton @rebron @brave/legacy_qa
The text was updated successfully, but these errors were encountered: