Feature #12690
Gather & analyze data about the Stretch cycle: test suite
Start date:
2017-06-13
Due date:
% Done:
10%
Feature Branch:
Type of work:
Research
Starter:
Affected tool:
Deliverable for:
Description
That’s one part of Feature #12615. It must be done before the Tails summit starts so we can decide something there. I’ve started this work on the blueprint, see the “XXX” I left in there for you in the “Test suite” section. This about the cost of “Keep the automated test suite up-to-date on feature/stretch”.
Subtasks
Related issues
Blocks Tails - |
Resolved | 2017-06-29 |
History
#1 Updated by Anonymous 2017-06-27 13:26:53
- Due date set to 2017-08-21
#2 Updated by anonym 2017-06-29 13:17:54
- blocks
Feature #13234: Core work 2017Q3: Foundations Team added
#3 Updated by anonym 2017-06-29 13:47:58
- blocked by deleted (
)Feature #13234: Core work 2017Q3: Foundations Team
#4 Updated by anonym 2017-06-29 13:48:48
- blocks
Feature #13239: Core work 2017Q3: Test suite maintenance added
#5 Updated by anonym 2017-06-29 13:49:44
- Assignee changed from anonym to intrigeri
- QA Check set to Info Needed
Please clarify what this ticket is about.
(I interpreted this ticket as looking at the actual test suite results to see how often real functionality breaks when being based on Debian Sid, but apparently it is not.)
#6 Updated by intrigeri 2017-06-29 15:21:47
- Description updated
- Assignee changed from intrigeri to anonym
- QA Check deleted (
Info Needed)
Clear enough, with the updated description and once you’ve read the relevant part of the blueprint?
#7 Updated by intrigeri 2017-08-30 06:52:16
- Status changed from In Progress to Rejected
I doubt we’ll get more data than what I gathered myself => closing.
#8 Updated by anonym 2017-09-28 18:56:07
- Target version changed from Tails_3.2 to Tails_3.3
#9 Updated by anonym 2017-09-28 19:00:09
- Target version changed from Tails_3.3 to Tails_3.2
#10 Updated by intrigeri 2017-11-25 15:26:23
- Due date deleted (
2017-08-21)