Closed
Bug 1029855
Opened 10 years ago
Closed 10 years ago
Run scripts for porting Thunderbird release notes to Bedrock
Categories
(Websites :: Nucleus, defect)
Websites
Nucleus
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: malexis, Assigned: giorgos)
References
Details
(Whiteboard: [kb=1548900] )
+++ This bug was initially created as a clone of Bug #1027892 +++
Comment 1•10 years ago
|
||
Hi Mark, will you please confirm that you are okay with us archiving the older release notes to the bedrock archive? And only moving the last 2-3 releases to RNA? Thanks
Flags: needinfo?(standard8)
Updated•10 years ago
|
Assignee: sancus → jeroentulp
Updated•10 years ago
|
Assignee: jeroentulp → nobody
Comment 2•10 years ago
|
||
(In reply to Cory Price [:ckprice] from comment #1) > Hi Mark, will you please confirm that you are okay with us archiving the > older release notes to the bedrock archive? Assuming they are still available at the same urls (or get redirected), that is fine. > And only moving the last 2-3 releases to RNA? It would be useful to get a minimum of: 31.0 31.1.0 31.1.1 31.1.2 33.0beta
Flags: needinfo?(standard8)
Assignee | ||
Comment 3•10 years ago
|
||
I'm working on a small script to automate the migration of release notes to rna. From the wiki I can find from the latest thunderbird, up until and version 14.0. Earlier versions either don't link anywhere or are not in a format that can be parsed. :standard8 is https://wiki.mozilla.org/Releases the canonical source for thunderbird releases? Do we have release notes prior version 14.0?
Flags: needinfo?(standard8)
Assignee | ||
Comment 4•10 years ago
|
||
Gist with script and generated python code to import notes: https://gist.github.com/glogiotatidis/d57dd6db0419c8e93839
Assignee | ||
Comment 5•10 years ago
|
||
Ok found the release notes in the SVN maze, updating the script.
Flags: needinfo?(standard8)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → giorgos
Status: NEW → ASSIGNED
OS: Mac OS X → All
Hardware: x86 → All
Assignee | ||
Comment 6•10 years ago
|
||
Thunderbird release notes and system requirements for versions < 30.0 will be archived (bug 1081917). Release notes and system requirements for versions: 30.0beta 31.0beta 31.0 31.1.0 31.1.1 31.1.2 32.0beta 33.0beta Will be migrated to RNA.
Assignee | ||
Comment 7•10 years ago
|
||
This gist creates Release and Note objects in RNA for the versions of comment #6. https://gist.github.com/glogiotatidis/d57dd6db0419c8e93839 :jgmize is it possible to run this on nucleus stage, verify and then run on prod?
Flags: needinfo?(jmize)
Comment 8•10 years ago
|
||
:giorgos I tested the gist locally and got an IndentationError on line 19, and it looks like there are several more errors like this. Would you mind fixing your gist and I'll try again?
Flags: needinfo?(jmize)
Assignee | ||
Comment 9•10 years ago
|
||
Apologies :jgmize, that's a copy/paste error. Can you please try again? Before running it again you'll have to delete releases and notes created: Note.objects.filter(releases__in=Release.objects.filter(product='Thunderbird')).delete() Release.objects.filter(product='Thunderbird').delete()
Flags: needinfo?(jmize)
Updated•10 years ago
|
Whiteboard: [kb=1548900]
Comment 10•10 years ago
|
||
:giorgos I took your gist as a base, and then created https://gist.github.com/jgmize/939f3f78d1f42691a7f7 which posts the data via the API and includes the latest release, 31.2.0. Tested and debugged locally, ran on stage and prod with no issues.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(jmize)
Resolution: --- → FIXED
Assignee | ||
Comment 11•10 years ago
|
||
Posting the data over RNA API unfortunately escaped the HTML parts of the release notes, resulting into this https://www.mozilla.org/en-US/thunderbird/31.0/system-requirements/ I tried locally without the leading spaces in the html lines and that seems to fix the issue. Updated gist here: https://gist.github.com/glogiotatidis/0c8282cbb64b778bab72 :jgmize can you please update the notes? Thanks!
Status: RESOLVED → REOPENED
Flags: needinfo?(jmize)
Resolution: FIXED → ---
Comment 12•10 years ago
|
||
Good catch, Giorgos, I missed the extra indentation level and it's associated effect on the markdown processing. While your script wouldn't work as-is, I just fixed the indentation levels in emacs and did some quick copy pasta work into the admin for each release. This can now be seen on each release in production.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Flags: needinfo?(jmize)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•