Feature #8852

Proactively check for upstream merge conflicts in our Tor Browser AppArmor profile

Added by intrigeri 2015-02-04 17:20:28 . Updated 2015-03-22 12:07:30 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Continuous Integration
Target version:
Tails_1.3.1
Start date:
2015-02-04
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

(As discussed on “[Tails-dev] Sandboxing Tor Browser: strategy for tracking ”upstream" AppArmor profile".)

Subtasks

Feature #8853: Set up a Git repository forked off upstream torbrowser-launcher's Resolved intrigeri

100
Feature #8854: Set up a daily Jenkins job that tries to merge upstream torbrowser-launcher's master branch into our own one Resolved intrigeri

100

Related issues

Related to Tails - Feature #5525: Sandbox the web browser Resolved 2015-01-24 2015-02-04

History

#1 Updated by intrigeri 2015-02-04 17:21:01

  • Affected tool set to Browser

#2 Updated by intrigeri 2015-02-04 17:23:21

#3 Updated by intrigeri 2015-03-04 10:39:12

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to bertagaz
  • QA Check set to Ready for QA

Done in the jenkins-job repo (d896da54^..) => please review, and mark as resolved once done.

#4 Updated by bertagaz 2015-03-15 12:40:36

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • QA Check changed from Ready for QA to Pass

Reviewed, sorry for the lag.

#5 Updated by BitingBird 2015-03-22 12:07:30

  • Target version changed from Tails_1.3.2 to Tails_1.3.1