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

Beta extension deployment #1070

Merged
merged 5 commits into from
May 9, 2024
Merged

Beta extension deployment #1070

merged 5 commits into from
May 9, 2024

Conversation

grod220
Copy link
Collaborator

@grod220 grod220 commented May 8, 2024

Closes #819

We now have a google group for prax beta testers: https://groups.google.com/a/penumbralabs.xyz/g/prax-beta-testers. This will allow us to push a private beta version of the extension, garner feedback from external contributors (i.e. passionate discord members). This serves as a kind of staging environment. Details of workflow in docs.

Note new colors for Beta extension.

Screenshot 2024-05-08 at 3 09 16 PM

@grod220 grod220 force-pushed the beta-ext-deployment branch 3 times, most recently from a69ee56 to a49c65f Compare May 8, 2024 12:55
@grod220 grod220 force-pushed the beta-ext-deployment branch from a49c65f to aaf670c Compare May 8, 2024 13:03
@grod220 grod220 force-pushed the beta-ext-deployment branch 2 times, most recently from b91df80 to 195c7ee Compare May 8, 2024 13:30
@grod220 grod220 changed the title WIP: Beta extension deployment Beta extension deployment May 8, 2024
@Valentine1898
Copy link
Contributor

We probably need to have not only the beta version of extension, but also deploy the beta version of minifront.
In fact, extension has very limited functionality, and there is almost nothing to test manually.
At the same time, if you test beta version of extension with prod version of minifront, it may create non-existing bugs, and new functionality cannot be tested.

@grod220
Copy link
Collaborator Author

grod220 commented May 8, 2024

but also deploy the beta version of minifront

Yep! Will create an issue for this. Should be quite easy to do.

Copy link
Contributor

@Valentine1898 Valentine1898 left a comment

Choose a reason for hiding this comment

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

LGTM

I wonder if it won't cause any conflicts when users have two wallet extensions installed (beta and prod)
At least it is not obvious which extension will be used

@TalDerei
Copy link
Contributor

TalDerei commented May 8, 2024

Screenshot 2024-05-08 at 10 21 13 AM

didn't know you have to pay a registration fee interesting (update: I see we describe this in the publishing markdown file!).

Copy link
Contributor

@TalDerei TalDerei left a comment

Choose a reason for hiding this comment

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

what time window are we targeting between how long beta testers will have to review the beta extension features and when the production version will be published? Won't this create time-delays not only for new features, but also for fixes for recently discovered bugs? For the latter case, is there a way to manually publish the production version and bypass the beta review?

@grod220 grod220 force-pushed the beta-ext-deployment branch from 195c7ee to b654382 Compare May 9, 2024 08:42
@grod220
Copy link
Collaborator Author

grod220 commented May 9, 2024

@TalDerei

  • Access to the chrome dev dashboard at the moment will be restricted to only a few internal team members fyi
  • It's entirely up to us to determine how long we wish for our extension to be tested in the new "staging" step via this private beta extension. For hot fixes, we can always set the prod-version of the extension to go live immediately after approval (like we are doing now). But with the new beta version, we have more flexibility to test new features and/or chain upgrades before they go live for everyone.

@grod220 grod220 merged commit e641e50 into main May 9, 2024
6 checks passed
@grod220 grod220 deleted the beta-ext-deployment branch May 9, 2024 08:49
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.

Extension "trusted testers" publish workflow
3 participants