Feature #9335

Add the coppersurfer.tk tracker to our Torrent

Added by intrigeri 2015-05-04 04:42:12 . Updated 2015-06-28 07:18:07 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2015-05-04
Due date:
% Done:

100%

Feature Branch:
doc/9335-add-coppersurfer-tracker
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We’ve decided this at the May, 2015 monthly meeting, following-up on the research done on Feature #9277.


Subtasks


Related issues

Related to Tails - Feature #9277: Research BitTorrent trackers we could use Resolved 2015-04-25

History

#1 Updated by intrigeri 2015-05-04 04:42:27

  • related to Feature #9277: Research BitTorrent trackers we could use added

#2 Updated by Dr_Whax 2015-05-14 14:03:37

  • QA Check set to Ready for QA
  • Feature Branch set to 9335-add-coppersurfer-tracker

#3 Updated by Dr_Whax 2015-05-14 14:04:26

  • Status changed from Confirmed to Fix committed

#4 Updated by BitingBird 2015-05-14 14:11:08

  • Status changed from Fix committed to In Progress
  • % Done changed from 0 to 30

You don’t have commit rights AFAIK so it will be commited after the review :)

#5 Updated by kytv 2015-05-14 14:18:26

  • Feature Branch changed from 9335-add-coppersurfer-tracker to drwhax:9335-add-coppersurfer-tracker

It should also be assigned to someone to do the QA work or unassigned.

(To make it easier for the reviewer, the commit is here

#6 Updated by intrigeri 2015-05-14 14:19:37

  • QA Check changed from Ready for QA to Dev Needed

Yay, progress on this front! :)

Note that “Fix committed” means the branch has been merged, which is not the case here yet AFAIK. Also, once ready you’ll want to de-assign this ticket from you: please read https://tails.boum.org/contribute/merge_policy/, in particular the “How to submit your changes” section. Thanks!

To end with, apparently your Git repo still contains the old, pre-rewrite history => please fix that before suggesting anyone adds it to their Git remotes. Shall I delete your repo and re-create an empty one? Then you can save your changes with git format-patch, delete your local clone, and get a fresh one.

#7 Updated by Dr_Whax 2015-05-14 14:24:15

  • QA Check deleted (Dev Needed)

intrigeri: please go ahead with what you just proposed.

reads merge policy

#8 Updated by Dr_Whax 2015-06-07 21:55:31

  • QA Check set to Ready for QA
  • Feature Branch changed from drwhax:9335-add-coppersurfer-tracker to drwhax:doc-9335-add-coppersurfer-tracker

#9 Updated by intrigeri 2015-06-08 07:12:10

  • Assignee changed from Dr_Whax to intrigeri

Yay, I’ll give an eye. DrWhax, please read https://tails.boum.org/contribute/merge_policy/submit/ :)

#10 Updated by intrigeri 2015-06-08 11:16:02

  • Assignee changed from intrigeri to Dr_Whax
  • % Done changed from 30 to 50
  • QA Check changed from Ready for QA to Info Needed
  • Feature Branch changed from drwhax:doc-9335-add-coppersurfer-tracker to doc/9335-add-coppersurfer-tracker

OK, looks good! I’ve merged current master into the topic branch, fixed the command line formatting a bit, and pushed to doc/9335-add-coppersurfer-tracker.

DrWhax, was the resulting torrent tested both for seeding and leeching? If not, can you please do it and then reassign to me?

#11 Updated by Dr_Whax 2015-06-28 06:50:59

  • Assignee changed from Dr_Whax to intrigeri

I have confirmed seeding and leeching is possible and peers are able to see each other.

#12 Updated by intrigeri 2015-06-28 07:13:51

  • QA Check changed from Info Needed to Ready for QA

#13 Updated by intrigeri 2015-06-28 07:18:07

  • 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

Merged!