Tails

#1 Updated by Anonymous 2018-10-16 13:40:58

• related to Bug #15838: Fix non-blocking issues identified during ASP code review added

#2 Updated by Anonymous 2018-10-16 13:42:52

• Subject changed from Improve ASP code to Improve ASP code: configuration window
• Deliverable for set to 319

#3 Updated by Anonymous 2018-10-16 13:46:07

• Target version set to Tails_3.11

#4 Updated by CyrilBrulebois 2018-12-16 14:04:00

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

#5 Updated by alant 2018-12-16 17:26:12

• Status changed from Confirmed to In Progress

Applied in changeset commit:tails|4fec7de061b5ea8c4b04dd2bdd80f7003653cc82.

#6 Updated by alant 2018-12-16 17:43:35

• QA Check set to Ready for QA
• Feature Branch set to bugfix/16060-improve-asp-conf-window

#7 Updated by alant 2018-12-16 17:44:05

• related to Bug #16226: Most branches FTBFS on Jenkins since the 3.11 release added

#8 Updated by anonym 2019-01-30 11:59:20

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

#9 Updated by intrigeri 2019-03-17 09:16:11

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

Even if this was submitted today, we would not have the reviewer resources to merge it in time for 3.13.

#12 Updated by Anonymous 2019-05-16 15:05:30

• Parent task deleted (Feature #14568)

I’m deleting the parent ticket, because I want to close the ASP project. Please let me know when you’ll work on this again, without urgency.

#13 Updated by Anonymous 2019-05-16 15:05:46

• related to Feature #14568: Additional Software Packages added

#14 Updated by CyrilBrulebois 2019-05-23 21:23:29

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

#15 Updated by intrigeri 2019-06-02 14:30:34

• QA Check deleted (Ready for QA)

(Preparing to drop the “QA Check” field as per “[Tails-dev] Proposal: Redmine workflow change”.)

#16 Updated by CyrilBrulebois 2019-07-10 10:34:09

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

#17 Updated by intrigeri 2019-08-30 17:30:29

• Target version deleted (Tails_3.16)

Hi!

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 Feature #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.

Cheers!

#18 Updated by alant 2020-03-08 18:47:54

• Assignee deleted (alant)

#19 Updated by alant 2020-03-08 18:59:12

• Status changed from In Progress to Rejected

As this ticket was a “maybe”, I propose to reject it.