Bug #7959

Release process and release manager docs need to be updated wrt. the migration to Tor Browser

Added by intrigeri 2014-09-27 10:05:15 . Updated 2014-10-08 07:46:20 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.2
Start date:
2014-09-27
Due date:
% Done:

100%

Feature Branch:
feature/tor-browser-bundle
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

Subtasks

Related issues

Related to Tails - Bug #8029: Document how to coordinate releases with the TBB Resolved 2014-10-08

History

#1 Updated by intrigeri 2014-09-27 10:16:11

  • Tracker changed from Feature to Bug

#2 Updated by intrigeri 2014-09-27 10:16:44

  • Subject changed from Release process and release manager doc needs to be updated wrt. the migration to Tor Browser to Release process and release manager docs need to be updated wrt. the migration to Tor Browser

#3 Updated by anonym 2014-09-28 16:58:47

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • Feature Branch set to feature/tor-browser-bundle

#4 Updated by intrigeri 2014-09-29 06:15:06

  • Status changed from Resolved to In Progress
  • Assignee set to anonym
  • % Done changed from 100 to 50
  • Looking at the Git history, it’s not obvious to me why don’t we need to update extensions.adblockplus.currentVersion anymore.
  • Why did the two sections about “Verify that the current source for Firefox” disappear? Tor Browser also has a build2, build3 etc. quite often, and so IMO we do need to check, at various steps of our release process, whether the fixes that went it after we built our ISO are worth doing some work again on our side.
  • Same question for the section about the web browser in contribute/release_process/Debian_security_updates: our upstream has changed, it’s not (mostly defunct, as an upstream, for our needs) Iceweasel anymore, it’s now Tor Browser, but we still do have an upstream, and coordinating with them is still needed (and actually, now much more realistic). So IMO this section ought to be rewritten for coordinating with the Tor Browser team, instead of simply deleted.

Otherwise, looks good at first glance!

#5 Updated by anonym 2014-10-08 07:38:02

  • related to Bug #8029: Document how to coordinate releases with the TBB added

#6 Updated by anonym 2014-10-08 07:38:29

  • Assignee changed from anonym to intrigeri
  • QA Check set to Ready for QA

intrigeri wrote:
> * Looking at the Git history, it’s not obvious to me why don’t we need to update extensions.adblockplus.currentVersion anymore.
> * Why did the two sections about “Verify that the current source for Firefox” disappear? Tor Browser also has a build2, build3 etc. quite often, and so IMO we do need to check, at various steps of our release process, whether the fixes that went it after we built our ISO are worth doing some work again on our side.

Fixed in commit 524a8ea.

> * Same question for the section about the web browser in contribute/release_process/Debian_security_updates: our upstream has changed, it’s not (mostly defunct, as an upstream, for our needs) Iceweasel anymore, it’s now Tor Browser, but we still do have an upstream, and coordinating with them is still needed (and actually, now much more realistic). So IMO this section ought to be rewritten for coordinating with the Tor Browser team, instead of simply deleted.

I don’t know what to write here before we’ve had that discussion with the TBB people. I created Bug #8029 so it’s not forgotten.

#7 Updated by intrigeri 2014-10-08 07:46:20

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass
  • Type of work changed from Code to Documentation