Tracking bug add Thunderbird release notes to RNA

RESOLVED FIXED

Status

Websites
Nucleus
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: malexis, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
Tracking bug for adding Thunderbird product to RNA

Tasks which will be broken out into dependency bugs:

- Get Mark [standard8] test up with testing account on Nucleus
- Add a new thunderbird product to RNA
- Build templates and views 
- system requirements
- script to copy everything (or manual copy paste work)
- move Thunderbird site to bedrock
- button support
- testing
(Reporter)

Updated

4 years ago
Blocks: 1029814
(Reporter)

Updated

4 years ago
No longer blocks: 1029814
Depends on: 1029814
(Reporter)

Updated

4 years ago
Depends on: 1029829
(Reporter)

Updated

4 years ago
Depends on: 1029838
(Reporter)

Updated

4 years ago
Depends on: 1029855
Depends on: 1081917
Depends on: 1081918
Just fyi, I've got a release coming up later today, the next one will be on 25th, so please let me know if I should be doing things in different places.
Depends on: 1099028

Comment 2

4 years ago
(In reply to Mark Banner (:standard8) from comment #1)
> Just fyi, I've got a release coming up later today, the next one will be on
> 25th, so please let me know if I should be doing things in different places.

Hi Mark,

Yes, you'll want to create new release notes in nucleus now. The easiest way to create the 32.0 release notes will be to base it on the 32.0 beta: go to https://nucleus.mozilla.org/admin/rna/release/?product__exact=Thunderbird and check the box next to the 32.0b release, then in the "Action" dropdown select "copy releases" and click the "Go" button. This will create a new release with a version of "copy-32.0beta". Click on that, then change the version and any other details that need to be updated. The "Notes" section at the bottom has "Edit" links and a few other features that might come in handy. Also note the "Make release specific" button next to each note-- be default, the same notes are related to the copy, so if you update a note it affects the releasenotes pages for each version that note is associated with, so if you want to update a note only on one specific release, then use that button first, then edit it.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.