You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Prepare release PR body with team sign-off checklist
274
274
local release_body="# 🚀 v${new_version} Testing & Release Quality Process
275
275
276
-
Hi Team,
276
+
Hi Team,
277
277
As part of our new **MetaMask Release Quality Process**, here’s a quick overview of the key processes, testing strategies, and milestones to ensure a smooth and high-quality deployment.
278
278
279
279
---
280
280
281
281
## 📋 Key Processes
282
282
283
283
### Testing Strategy
284
-
- **Developer Teams:**
285
-
Conduct regression and exploratory testing for your functional areas, including automated and manual tests for critical workflows.
286
-
- **QA Team:**
287
-
Focus on exploratory testing across the wallet, prioritize high-impact areas, and triage any Sentry errors found during testing.
288
-
- **Customer Success Team:**
284
+
- **Developer Teams:**
285
+
Conduct regression and exploratory testing for your functional areas, including automated and manual tests for critical workflows.
286
+
- **QA Team:**
287
+
Focus on exploratory testing across the wallet, prioritize high-impact areas, and triage any Sentry errors found during testing.
288
+
- **Customer Success Team:**
289
289
Validate new functionalities and provide feedback to support release monitoring.
290
290
291
291
### GitHub Signoff
292
-
- Each team must **sign off on the Release Candidate (RC)** via GitHub by the end of the validation timeline (**Tuesday EOD PT**).
292
+
- Each team must **sign off on the Release Candidate (RC)** via GitHub by the end of the validation timeline (**Tuesday EOD PT**).
293
293
- Ensure all tests outlined in the Testing Plan are executed, and any identified issues are addressed.
294
294
295
295
### Issue Resolution
296
-
- **Resolve all Release Blockers** (Sev0 and Sev1) by **Tuesday EOD PT**.
296
+
- **Resolve all Release Blockers** (Sev0 and Sev1) by **Tuesday EOD PT**.
297
297
- For unresolved blockers, PRs may be reverted, or feature flags disabled to maintain release quality and timelines.
298
298
299
299
### Cherry-Picking Criteria
300
-
- Only **critical fixes** meeting outlined criteria will be cherry-picked.
300
+
- Only **critical fixes** meeting outlined criteria will be cherry-picked.
301
301
- Developers must ensure these fixes are thoroughly reviewed, tested, and merged by **Tuesday EOD PT**.
302
302
303
303
---
304
304
305
305
## 🗓️ Timeline and Milestones
306
306
307
-
1. **Today (Friday):** Begin Release Candidate validation.
308
-
2. **Tuesday EOD PT:** Finalize RC with all fixes and cherry-picks.
309
-
3. **Wednesday:** Buffer day for final checks.
310
-
4. **Thursday:** Submit release to app stores and begin rollout to 1% of users.
311
-
5. **Monday:** Scale deployment to 10%.
307
+
1. **Today (Friday):** Begin Release Candidate validation.
308
+
2. **Tuesday EOD PT:** Finalize RC with all fixes and cherry-picks.
309
+
3. **Wednesday:** Buffer day for final checks.
310
+
4. **Thursday:** Submit release to app stores and begin rollout to 1% of users.
311
+
5. **Monday:** Scale deployment to 10%.
312
312
6. **Tuesday:** Full rollout to 100%.
313
313
314
314
---
@@ -320,9 +320,9 @@ Each team is responsible for signing off via GitHub. Use the checkbox below to t
320
320
# Team sign-off checklist
321
321
- [ ] ${platform_team_name}
322
322
323
-
This process is a major step forward in ensuring release stability and quality. Let’s stay aligned and make this release a success! 🚀
323
+
This process is a major step forward in ensuring release stability and quality. Let’s stay aligned and make this release a success! 🚀
324
324
325
-
Feel free to reach out if you have questions or need clarification.
325
+
Feel free to reach out if you have questions or need clarification.
326
326
327
327
Many thanks in advance
328
328
@@ -381,8 +381,8 @@ create_changelog_pr() {
381
381
echo"Previous version is not a recognized release branch pattern. Treating as tag or SHA: ${previous_version_ref}"
382
382
fi
383
383
384
-
# Switch to github-tools directory
385
-
cd ./github-tools/
384
+
# Switch to .github-tools directory
385
+
cd ./.github-tools/
386
386
ls -ltra
387
387
corepack prepare yarn@4.5.1 --activate
388
388
# This can't be done from the actions context layer due to the upstream repository having it's own context set with yarn
@@ -401,7 +401,7 @@ create_changelog_pr() {
401
401
# # Create a new Release Sheet Page for the new version with our commits.csv content
0 commit comments