document hg certificate renewal process
Categories
(Developer Services :: Mercurial: hg.mozilla.org, enhancement)
Tracking
(Not tracked)
People
(Reporter: kmoir, Assigned: lars)
References
Details
Attachments
(1 file)
| Reporter | ||
Comment 1•7 years ago
|
||
| Reporter | ||
Updated•7 years ago
|
| Assignee | ||
Comment 2•7 years ago
|
||
Where should this documentation be published? My current drafts are within Google Docs, but I assume they'll eventually end up in Mana or elsewhere?
Comment 3•7 years ago
|
||
Either Mana or the version-control-tools docs. I'd prefer the vct docs, personally.
| Assignee | ||
Comment 4•6 years ago
|
||
Current working draft is https://docs.google.com/document/d/1hqqWQ8T4BtB55Bnwrmj89zuLjUBb2vnHuAl_AjpY4fs/edit?usp=sharing
Once this is complete, I will translate it to the vct docs.
:sheehan is it possible to get copies of all the public email announcements done during the last transition? This will help me verify order of actions and the timing of my instructions.
Comment 5•6 years ago
|
||
Bug 1495464 comment 3 contains two example emails, and the most recent notice sent to dev-platform is here.
| Assignee | ||
Comment 6•6 years ago
|
||
In my documentation, I want to include all the locations to which the user cert announcement should be sent. The announcement in mozilla.dev.platfrom googlegroup shows an obfuscated list of "other recipients". I can infer the complete name of three of the lists, but I'm unfamiliar with the other three. :conner, do you know the full addresses of the first three below?
<firef...@mozilla.org>
<firef...@mozilla.com>
<auto-...@mozilla.com>
<dev-version-control@lists.mozilla.org>
<release-engineering@lists.mozilla.org>
<dev-platform@lists.mozilla.org>
Comment 7•6 years ago
|
||
My best guess is that "auto-" is "auto-tools@mozilla.com". Not sure about the other two. Sorry I can't be of more assistance!
| Assignee | ||
Comment 8•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Description
•