Bug #11121

Adjust our release process to publish torrents for betas and RCs

Added by sajolida 2016-02-13 12:13:11 . Updated 2016-02-25 18:14:41 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-02-13
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We decided to do this in Feature #10915, now we need to adjust the release process documentation.


Subtasks


Related issues

Related to Tails - Feature #11127: Stop distributing detached signatures of Torrent files Rejected 2016-02-14
Related to Tails - Bug #11157: Link to the detached signature of the ISO in the torrent documentation Rejected 2016-02-22

History

#1 Updated by sajolida 2016-02-13 12:13:39

  • Assignee set to anonym

anonym: do you mind doing this in time for 2.2?

#2 Updated by anonym 2016-02-13 12:35:17

  • Assignee changed from anonym to sajolida
  • QA Check set to Info Needed

sajolida wrote:
> anonym: do you mind doing this in time for 2.2?

Not at all! However, how should it (link and signature) be presented in the Call for testing? Could you perhaps prepare that part so I don’t make something ugly! :)

#3 Updated by sajolida 2016-02-15 14:31:06

  • Subject changed from Publishing torrents for betas and RCs to Adjust our release process to publish torrents for betas and RCs
  • Assignee changed from sajolida to anonym
  • QA Check deleted (Info Needed)

I’ve already linked to the Torrent file from the call for testing in web/11119-2.2-rc1, see Feature #11119. This ticket is about updating the release process. Sorry for being unclear. I’m clarifying the title now.

#4 Updated by anonym 2016-02-25 00:52:53

  • Status changed from Confirmed to In Progress
  • Assignee changed from anonym to sajolida
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

sajolida wrote:
> I’ve already linked to the Torrent file from the call for testing in web/11119-2.2-rc1, see Feature #11119. This ticket is about updating the release process. Sorry for being unclear. I’m clarifying the title now.

Got it!

So, I think that the only missing step is to copy the .torrent into the correct directory, see commit:43bf0d9. In other words, we don’t care about the .sig file, right? I guess it’s the same for the non-RC releases, too? If so, I can remove the part about generating that .torrent signatures altoghether.

#5 Updated by sajolida 2016-02-25 15:35:13

  • related to Feature #11127: Stop distributing detached signatures of Torrent files added

#6 Updated by sajolida 2016-02-25 15:35:18

  • related to Bug #11157: Link to the detached signature of the ISO in the torrent documentation added

#7 Updated by sajolida 2016-02-25 15:37:56

  • Assignee changed from sajolida to anonym
  • QA Check changed from Ready for QA to Dev Needed

Actually, the discussion in Feature #11127#note-7 made a good technical point in favor the signature of the Torrent file, so now I think we should keep them (and I’ll link them in Bug #11157). Though the UX trade-off still seems pretty weak to me :)

#8 Updated by anonym 2016-02-25 18:12:03

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Dev Needed to Pass

Fixed in commits commit:43bf0d91 and commit:fae54e82.

#9 Updated by anonym 2016-02-25 18:14:41

  • Status changed from Fix committed to Resolved