https://wiki.mozilla.org/Release_Management/Release_Process should be updated

With the devedition in parallel of nightly
With the nightly soft freeze

Create a page for Nightly backouts and respin process

When and why we want to back out a patch on Nightly
How to find the patch to back out
Who to ping and where
How we should communicate about it externally and internally
Should we respin or not depending on the next nightly update
Blocking automatic updates to mitigate impact

Updates to Release Notes pages

https://wiki.mozilla.org/index.php?title=Release_Management/Relnotes_rules&oldid=1190084

remove mentions of Aurora
link to https://youtu.be/G6VeZyOP_Rk
Indicate that we have release notes for nightly too but not fennec nightly
Update links to point to recent relnotes
probably turn the “relnote-firefox tracking flag values" into a table for readability
We also have https://wiki.mozilla.org/Release_Management/Release_Notes ...

Recover past articles on channel blog

We deleted the old Channel blog however I discovered that we actually had good articles articles there linked from the wiki.

I updated the links in our wiki to point to the Wayback Machine snapshot:

We should probably rewrite/update those and either put them on the current blog or turn them into wiki pages.

Dealing with regressions document

We should have a document explaining how we manage regressions:

What RM do
What developers have to do
Bugzilla process -> regression keyword, status flags, reopening bugs…
mozregression
uplift request if the regression affects beta/release
How to handle regressions when all the work is done on Github including the bug tracker
link to respin process if the regression is on nightly and is important

Add process tag to process pages

All pages documenting a process should have the [[Category:Release_Management:Processes]]
tag

Update Nightly cycle action items for RM

https://wiki.mozilla.org/index.php?title=Release_Management/Nightly&oldid=1136006

This page lists the tasks for RelMan during the Nightly cycle
Beginning of a new cycle

Update the version number on Ship-it on merge day when mozilla-central (https://hg.mozilla.org/mozilla-central/file/tip/browser/config/version.txt) is updated with a new version number
Ask for a push of product-details to production once we have all the locales built
Copy the previous release notes template in Nucleus with the new version number

During the cycle:

Add that we watch all commits for interesting features
Add that interesting changes should be communicated to our alpha-testers via Twitter
Interesting features visible to the end user should have the relnote flag set
Write Release Notes on the fly
Watch reports on Twitter, IRC and other communication channels about major regressions. Ask for backout of a patch if the end-user impact may lead to loosing alpha testers.

End of cycle:

Check that there is no visual regression on the WNP caused by template changes on mozilla.org or gecko changes a week before merge day

Add RELEASE_MANAGEMENT_UPDATE_NEEDED to pages needing it

Add {{RELEASE_MANAGEMENT_UPDATE_NEEDED}} on top of all pages that need an update

Create a process card template

We have the summarized section, the full section and we could have a process card that lists common points which answer roughly to some of the who/when/why/how/what questions.

The process and summarized process sections also go into these questions but are mostly focused on the how.

The card would respond to the what, why, when, who questions so they give an overview of the process for people that are not going to do the process but need to understand what the process means organization-wise.

Release_Management.wiki cleanup

Source Page:
https://wiki.mozilla.org/index.php?title=Release_Management&oldid=1177887

TODO

TOC:

update logo
Remove dead link on logo

CONTRIBUTE SECTION:

Google Play scripts to upload APK and manage translations
-> links are 404 new place is https://github.com/mozilla-releng/mozapkpublisher/

TEAM INFO:

remove "Release_Management/Quarterly_Goals for the relman team"
-> last goals listed are 2015

COMMUNICATION CHANNELS:

add @firefoxnightly twitter
add blog
add #release-coordination Slack channel

MEETINGS:

add UTC times like on https://wiki.mozilla.org/Firefox/Channels/Meetings
Release sign-off meeting
->The links are dead, last meeting notes are for Firefox 27
https://wiki.mozilla.org/Releases/Firefox_27/Final_Signoffs remove as this is now part of the Channel Meeting that we already link to

CALENDAR UPDATING

check that the steps still work with the new google calendar UX
-> step are completely different, updated and added a direct sharing link
Calendar link shouldn't be the full URL

TEAM RESOURCES

remove all aurora mentions in text
remove "Aurora Landing Process What we do during the Aurora cycle" and put an Obsolete warning on the top of the linked page
remove "Aurora channel Blockers and Regressions"
"Hot fix process documentation" -> replace with System add-on documentation
Beta 44 Release Checklist -> updated link and reworded to not have a version number

DASHBOARD LINKS

remove "Aurora, Beta Uplifts Dashboard"
remove "Aurora channel Blockers and Regressions"
Add delivery dashboard https://mozilla.github.io/delivery-dashboard/

TOOLS

Added product-details
remove "Our Release Survey" link, marked https://wiki.mozilla.org/Release_Management/Release_Survey as obsolete
remove "Firefox Triage Dashboard" link

OTHER

remove all '"B2G pages" section
remove Chinese repack section

ESR page

catlee | https://wiki.mozilla.org/Release_Management/ESR_Landing_Process needs updating now that ESR52 is gone

Use nicer titles for all pages

All our pages contain the Full page name based on the url

ex:
https://wiki.mozilla.org/Release_Management/Relnotes_rules
Page Title: Release Management/Relnotes rules

We can remove the Release_Management namespace with this rule:
{{DISPLAYTITLE:title to be displayed}}

Ex in the case above:
{{DISPLAYTITLE:Release Notes Rules}}

We shoud update all our pages with a clear name.

Get a slot on wikimo front page

We should have a slot on the wiki front page for discoverability of the pages that our devs and contributors are always looking for, namely:

Release owners
Release Calendar
Release Notes
Release process

The front page is not editable and clearly unmaintained so we need to check who can update it or if we can get editing rights on it.

Create header template on wiki for pages needing an update

Similarly to the header template indicating that a page is obsolete and no longer relevant, I think we need a template indicating that a page content is still OK but may not be completely accurate or current. We have pages which last update is like 2014 altough what is described looks mostly correct to me.

Something along the lines of:

Warning: Our team is working on updating all of our Release Management documentation. This page hasn't been udated recently and may not be 100% up to date or accurate. In case of doubt, don't hesitate to contact our release managers directly.

Release notes page, dot releases

For a dot release, we add the bug numbers to each note
Add a link to the main note: Reference link to 60.0 release notes
-> mark it as release specific, no tag

Create a page that describes the documentation writing process itself

https://wiki.mozilla.org/Release_Management/Documentation_guidelines
So as to have some consistency in documentation and share knowledge, we should have a page explaining how to create documentation for our team on the wiki.

Explain the various header templates we have (stub, obsolete, in progress)
All pages should be in the Release_Management namespace
Explain which categories we use: currently only Processes and the general Release_Management one
Explain how to redirect an existing page
Explain how to rename a page
Explain the "summarized process" part of process pages
Styling tips (see with Liz)
List channel versions templates

Create a category for Processes

All pages which document a process should be indexed in a special category page, this way we have a dynamic list of all our processes.
[[Category:Release_Management:Processes]]

Team_members update

Source: https://wiki.mozilla.org/index.php?title=Release_Management/Team_members&oldid=1167777

TODO

QUESTIONS

Add timezone next to member?

Document What's New page process

It's a bit unclear what we should do about what's new pages

Release_Process.wiki cleanup

Source page
https://wiki.mozilla.org/index.php?title=Release_Management/Release_Process&oldid=1187936

TODO

QUESTIONS

More developer edition data?
Document week of release branch merges?
put a more detailed timeline?

OTHER INFORMATION

jlorenzo's schema https://bug1430593.bmoattachments.org/attachment.cgi?id=8942658

Nightly Code Soft freeze ends when we change the version number on merge day in mozilla-central, the Monday.

Create a STUB header template

Create a header to indicate that a page is a stub for content that needs to be written in the future.

Move obsolete pages to Archives category

[[Category: Release Management]] ->[[Category: RelManArchive]]

Create Product Details page

https://wiki.mozilla.org/Release_Management/Product_details only has 12 words in it, if we want it to be the source of versions truth from release management we should document it better.

Document:

Schema and purpose of each individual JSON file
Difference between ship it, product-details, product-details-json repo
Weirdness in properties schema and naming
Where to report bugs

Our calendar is outside of the Release Management domain

url: https://wiki.mozilla.org/RapidRelease/Calendar

The RapidRelease namespace is already redirected to Release_Management.

We should rename this page to be in our namespace and fix the inconsistency:
-> https://wiki.mozilla.org/Release_Management/Calendar

Add process cards to all existing Process pages

-> only do that to up to date pages, future pages and pages needing a full update willl have the card added as part of their updating process as an item in their specific issue

Inventory of our Wiki pages and action items

https://wiki.mozilla.org/Category:Release_Management

(items dealt with in a specific issue should have their checkbox selected)

TODO

Add Obsolete warning at top:

Oldest pages : add Update Needed warning at top:

Needs a clean up

Needs new content

Needs content merged

https://wiki.mozilla.org/Release_Management/Release_Notes & https://wiki.mozilla.org/Release_Management/Relnotes_rules issue #13

Belongs to Other teams but categorized as Release Management

Needs a discussion

Release notes page

Clarify that people have to click on the "add to comment" link to get a form prefilled in the comment.

Obsolete content template

Create a template allowing to indicate that a page is obsolete

Template: https://wiki.mozilla.org/Template:RELEASE_MANAGEMENT_OBSOLETE

Insert at the top of the page with:
{{RELEASE_MANAGEMENT_OBSOLETE}}

Update Glossary page

REO https://wiki.mozilla.org/Platform#Regression_Engineering_Owner_.28REO.29
GTB (Go To Build)
First Merge Day vs Merge Day

Rewrite Autonag page

[15:00]	calixte	https://www.chromium.org/issue-tracking/autotriage
[15:01]	calixte	https://wiki.mozilla.org/Release_Management/autonag
[15:05]	calixte	https://monorail-prod.appspot.com/p/chromium/issues/detail?id=797243#c20

Update Onboarding page

https://wiki.mozilla.org/index.php?title=Release_Management/Onboarding&oldid=1191787

glossary page

Chemspill, nightly soft freeze, relman, acronyms, internal tools names such as Balrog or Nucleus, jargon. I think we should have a glossary page.

pascalchevrel / rmdocs Goto Github PK

rmdocs's Introduction

rmdocs

rmdocs's People

Contributors

Watchers

rmdocs's Issues

TODO

TODO

QUESTIONS

TODO

QUESTIONS

OTHER INFORMATION

TODO

Add Obsolete warning at top:

Oldest pages : add Update Needed warning at top:

Needs a clean up

Needs new content

Needs content merged

Belongs to Other teams but categorized as Release Management

Needs a discussion

Recommend Projects

Recommend Topics

Recommend Org