Deal with April 2017 false positive scenarios
As defined in #10993, check is there are still some of them and tag them as fragile if any (see #10288).
- Category set to Continuous Integration
Now that we are close to 3.0 and
feature/stretch being merged, let's down-prioritize new robustness issues in
devel in the sense that we ignore the issue unless we find proof that it also affects
feature/stretch. This might mean that we ignore an issue that actually affects
feature/stretch but isn't visible due to something breaking earlier in the affected tests, but let's prefer that risk over identifying and tracking issues that don't affect Tails after Jessie.
- Target version changed from Tails_3.0 to Tails_3.0~rc1
Whenever you do this work, it would be very nice to look for issues I've listed on #11983: knowing whether we also see them on feature/stretch would help a lot evaluate the impact of #5630.
Also look at
- Blocks deleted (Feature #12536: Have the devel branch based on Stretch)
- Status changed from Confirmed to Rejected
- Assignee deleted (
I lost the feature/stretch data by mistake.
Also available in: Atom