Bug #15508

Clean up tags in persistence-setup.git

Added by intrigeri almost 2 years ago. Updated 5 months ago.

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:
Affected tool:


In the last couple months one of us (presumably bertagaz, who touches this repo last) pushed to persistence-setup.git the tags from… whisperback.git, e.g. debian/1.6.28+python3.1.

Please clean this up by deleting every tag that's not about persistence-setup. Thanks in advance!


#1 Updated by bertagaz over 1 year ago

  • Target version changed from Tails_3.7 to Tails_3.8

#2 Updated by intrigeri over 1 year ago

  • Target version changed from Tails_3.8 to Tails_3.9

#3 Updated by intrigeri over 1 year ago

  • Target version changed from Tails_3.9 to Tails_3.10.1

#4 Updated by intrigeri about 1 year ago

  • Target version changed from Tails_3.10.1 to Tails_3.11

#5 Updated by CyrilBrulebois about 1 year ago

  • Target version changed from Tails_3.11 to Tails_3.12

#6 Updated by anonym 12 months ago

  • Target version changed from Tails_3.12 to Tails_3.13

#7 Updated by CyrilBrulebois 10 months ago

  • Target version changed from Tails_3.13 to Tails_3.14

#8 Updated by CyrilBrulebois 8 months ago

  • Target version changed from Tails_3.14 to Tails_3.15

#9 Updated by CyrilBrulebois 7 months ago

  • Target version changed from Tails_3.15 to Tails_3.16

#10 Updated by intrigeri 5 months ago

  • Target version deleted (Tails_3.16)


We've set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to:

  • better reflect your plans;
  • bring down your amount of work-in-progress to a sustainable level;
  • encourage team work and increase the chances that someone finishes the work;
  • avoid a human doing ticket triaging and asking you the same questions on each such ticket.

In particular, this process identifies:

  • Stalled work-in-progress
  • Reviews waiting for a long time

However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I'm doing on this ticket.

You now have a few options, such as:

  • Deassign yourself. That's fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
  • If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable "Target version". This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today's choice.


Also available in: Atom PDF