Bug #11360

Integrate Onion Circuits into our release process

Added by anonym 2016-04-22 07:08:14 . Updated 2016-05-22 16:00:06 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.4
Start date:
2016-04-22
Due date:
% Done:

0%

Feature Branch:
Type of work:
Discuss
Blueprint:

Starter:
Affected tool:
Onion Circuits
Deliverable for:

Description

It’s currently not listed in the “Upgrade bundled binary Debian packages” section of wiki/src/contribute/release_process.mdwn.

Subtasks

History

#1 Updated by anonym 2016-04-22 07:08:44

  • Description updated

#2 Updated by anonym 2016-04-22 08:10:20

  • blocked by Bug #11361: Document how to build Onion Circuits Debian packages added

#3 Updated by anonym 2016-04-22 08:10:52

  • Target version changed from Tails_2.3 to Tails_2.4

Delaying due to Bug #11361. Also see Feature #11160#note-10; maybe this ticket should be blocked by Feature #11160?

#4 Updated by intrigeri 2016-05-18 09:46:34

  • QA Check set to Info Needed

Actually, I don’t think we should do that.

IMO we should handle Onion Circuits just like MAT and other similar packages, for which we have a pretty close relationship to upstream, and that we’re maintaining in Debian:

  • we contribute upstream, and some of us happen to be the upstream lead maintainers; upstream is ready to adjust their release timing depending on the Tails release cycle;
  • most of the time, the work that’s done upstream flows into Debian, then into backports, and then into Tails, without having any additional releasing/packaging work to do at Tails release time (that’s what I’m trying to do in Feature #11443);
  • whenever we are in a hurry to get a fix in Tails, that’s not been released upstream yet, we can either:
    • in most cases: get the fix via Debian or via our custom APT repo, as a quilt patch added to the packaging; that’s the kind of temporary exceptional treatment we give to 2k other packages, I don’t see why we should normalize the “we have to maintain a delta” situation for Onion Circuits specifically; I know that’s what you had to do for Tails 2.3, and I certainly hope that it won’t be the case too often (granted, perhaps a few more times as Onion Circuits is pretty new, but I expect the situation will quickly stabilize);
    • worst case, if the fix is so invasive that it really requires an upstream release: we can exceptionally wear our upstream contributors hat, put a release out there, and then Sascha or other pkg-privacy people will get it into Debian.

How does it sound?

#5 Updated by intrigeri 2016-05-18 09:46:45

  • Type of work changed from Contributors documentation to Discuss

#6 Updated by anonym 2016-05-22 15:59:15

  • blocks deleted (Bug #11361: Document how to build Onion Circuits Debian packages)

#7 Updated by anonym 2016-05-22 16:00:06

  • Status changed from Confirmed to Rejected
  • Assignee deleted (anonym)
  • QA Check deleted (Info Needed)

Sounds good to me. Rejecting, then, and moving on to Bug #11361.