MetaMask / MetaMask/metamask-extension

As a MetaMask stakeholder (PM, CS, marketing, etc) I want to be able to easily know the release status of a change

Open
#20,476 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

As a MetaMask stakeholder (PM, CS, marketing, etc) I want to be able to ask "Where is PR #99999?" and have an answer like one of the following:

- It is in review.
- It is merged to developed, but not in an RC. It will be part of RC-v1.2.3, which should begin rollout on April 1, 2020
- It is in RC-v1.2.3, which is currently in QA and which should begin rollout on April 1, 2020
- It is in RC-v1.2.3, which has been submitted to extension stores, and should begin rollout on April 1, 2020
- It is in v1.2.3, which began rollout on April 1, 2020
- It was in v1.2.3, which completed rollout on April 1, 2020

Stakeholders should be able to get these answers through easy and automated means, and not have to ask other people

Contributor guide

Open the contributing guide

Research direction

Start by mapping the release states named in the issue: PR review, developed, RC, QA, extension-store submission, and rollout. Define how an automated response for a PR such as #99999 would obtain and present each status, including the planned rollout date; done means stakeholders can retrieve these answers without asking another person.

Written by the indexing model from the issue text.

Assessment

Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.