Skip to content

Create a support article with useful information about the upgrade #1918

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

Closed
bsclifton opened this issue Oct 31, 2018 · 2 comments
Closed

Create a support article with useful information about the upgrade #1918

bsclifton opened this issue Oct 31, 2018 · 2 comments

Comments

@bsclifton
Copy link
Member

Some important goals for the support article

  • Describe why this upgrade is needed
  • Explain the possible impact to the user
    • needing to import, if that part fails
    • Brave Rewards impact (items that were pinned may need to be resolved manually to direct tips)
    • How default browser setting is affected (and how to set Brave Core as new default browser)

The article can then also contain information on:

  • where the Muon profile lives (and letting them know it's not touched during the upgrade)
  • how to launch the old browser (in case they need to save Brave Payments reports, etc)
  • how to grab extension data (ex: MetaMask)
  • how to find/install extensions they may have had enabled in Muon Brave
@bbondy bbondy added this to the 1.x Backlog milestone Nov 5, 2018
@diracdeltas
Copy link
Member

can someone let me see the article? login is [email protected] (google auth)

@bsclifton
Copy link
Member Author

@diracdeltas both you and @jumde should have access now 😄 Since this article has been created and has a decent amount of content, I'll close the issue. We'll of course want to review before launch 😄

@bsclifton bsclifton modified the milestones: 1.x Backlog, 0.56.x - Release Hotfix 1 Nov 9, 2018
@bsclifton bsclifton modified the milestones: 0.57.x - Beta, Dupe / Invalid / Not actionable Nov 29, 2018
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants