Project

General

Profile

Feature #8852

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

Added by intrigeri over 4 years ago. Updated over 4 years ago.

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

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:
Browser

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'sResolvedintrigeri

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


Related issues

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

History

#1 Updated by intrigeri over 4 years ago

  • Affected tool set to Browser

#2 Updated by intrigeri over 4 years ago

#3 Updated by intrigeri over 4 years ago

  • 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 over 4 years ago

  • 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 over 4 years ago

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

Also available in: Atom PDF