Project

General

Profile

Bug #16060

Improve ASP code: configuration window

Added by u about 1 year ago. Updated 3 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
10/16/2018
Due date:
% Done:

0%

Feature Branch:
bugfix/16060-improve-asp-conf-window
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Additional Software Packages

Description

Reported from #15838

configuration-window.ui:

Maybe remove the install_label text, because it's overwritten in update_packages_list() anyway

Related issues

Related to Tails - Bug #15838: Fix non-blocking issues identified during ASP code review Resolved 09/26/2018
Related to Tails - Bug #16226: Most branches FTBFS on Jenkins since the 3.11 release Resolved 12/15/2018
Related to Tails - Feature #14568: Additional Software Packages Resolved 12/11/2013 06/26/2018

Associated revisions

Revision 4fec7de0 (diff)
Added by alant 12 months ago

ASP: deduplicate label text in configuration window

Will-fix: #16060

History

#1 Updated by u about 1 year ago

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

#2 Updated by u about 1 year ago

  • Subject changed from Improve ASP code to Improve ASP code: configuration window

#3 Updated by u about 1 year ago

  • Target version set to Tails_3.11

#4 Updated by CyrilBrulebois 12 months ago

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

#5 Updated by alant 12 months ago

  • Status changed from Confirmed to In Progress

#6 Updated by alant 12 months ago

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

#7 Updated by alant 12 months ago

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

#8 Updated by anonym 10 months ago

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

#9 Updated by intrigeri 9 months ago

  • 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.

#10 Updated by u 9 months ago

@alant: is this ready for QA for intrigeri?

#11 Updated by intrigeri 8 months ago

alant: is this ready for QA for intrigeri?

@u, I think @alant uses "Ready for QA" + "keep assigned to himself" as a way to express something along the lines of "I believe I've resolved it, next step is to build, test, and confirm the problem it actually solved".

#12 Updated by u 7 months ago

  • Parent task deleted (#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 u 7 months ago

#14 Updated by CyrilBrulebois 7 months ago

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

#15 Updated by intrigeri 6 months ago

  • 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 5 months ago

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

#17 Updated by intrigeri 3 months ago

  • 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 #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!

Also available in: Atom PDF