-
Notifications
You must be signed in to change notification settings - Fork 4.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
Mobile Release v1.54.0 #32297
Mobile Release v1.54.0 #32297
Conversation
Size Change: 0 B Total Size: 1.85 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Per the release checklist, we shouldn't pull trunk
in or merge this until after we finish the "Integrate the Release" section and begin the "Sync the Release to Development Branches" section.
I noticed that there's no |
Whoops. Yes, for better or worse it is not an explicit task in the release scenario. It is a checklist item on the GB Mobile PR itself. However, it lists two locations in one task. I have overlooked the second location myself multiple times. It may be worth splitting the locations into two separate tasks in the PR.
|
Yeah, I was thinking of adding an extra step in the Release Checklist Template to make this step clearer, wdyt? |
I'm torn. It's a long checklist. 😄 However, having checklists in multiple locations isn't a great aspect either. 🙃 At this point, I definitely think we need to split the two locations into separate tasks. If we add those tasks to the release scenario checklist, then I think we should remove them from the PR checklist. Having the same task in two locations would likely lead to people overlooking tasks they think they already completed due to repetition/noise. |
You're right, it's getting too long to keep adding items 😄 , let's try to avoid it 👍 .
I'm leaning more on the option of splitting the two locations into separate tasks to make it clearer. EDIT: I've just realized that the change has to be done in the release pull request template. |
Description
Release 1.54.0 of the react-native-editor and Gutenberg-Mobile.
For more information about this release and testing instructions, please see the related Gutenberg-Mobile PR: wordpress-mobile/gutenberg-mobile#3559
Checklist:
*.native.js
files for terms that need renaming or removal).