Tails

#8 Updated by intrigeri 2020-02-23 06:58:51

(As per timeline discussion we had yesterday. This is about finishing the work, and possibly merging it into devel, not about merging it into stable yet: the current plan is to release this in 4.5, not 4.4.)

#9 Updated by intrigeri 2020-02-23 06:59:34

Gah, I documented a no-op change, ah ah. Sorry for the noise.

#11 Updated by CyrilBrulebois 2020-03-11 06:16:28

FYI: Ticket metadata is slightly confusing, as it seems to be resolved in Tails 4.4, which it isn’t? (Currently checking debian/changelog vs. the “Completed for the next release” view, this pops up.)

#12 Updated by intrigeri 2020-03-11 08:59:59

hi @CyrilBrulebois,

> FYI: Ticket metadata is slightly confusing, as it seems to be resolved in Tails 4.4, which it isn’t? (Currently checking debian/changelog vs. the “Completed for the next release” view, this pops up.)

I see.

Technically, we did create overlayfs-based IUKs v2 for the test suite. But it’s true that it’s orthogonal to 4.4.

To track progress on larger projects, we often close individual subtasks as resolved as soon as they’ve been completed.
I understand that the “Target version” can thus get confusing.

I believe that with GitLab, this problem will occur less often, because it has no child issue support but it has “list of tasks” (checklist) support. But still, I think it’ll still happen occasionally. To avoid that entirely, I think we would need to take a step back and rethink how we track projects. I’d like to come back to this after we’ve spent 6+ months on GitLab and have data about how it’ll impact our workflows in practice (there’s only so much we can guess before we actually start using this new tool). Fair enough?

If you think that’s important enough to warrant making sure we don’t forget about it, let me know and I’ll give myself a ticket!

#13 Updated by CyrilBrulebois 2020-03-13 06:42:34

Hey @intrigeri!

Thanks for the explanation, it makes a lot of sense.

I really don’t mind the current setup/workflow; I was just a little surprised, possibly because I didn’t encounter this situation before (or maybe there was a bigger list of issues and I missed similar tickets). That’s why I did mention it in passing, just making sure I wasn’t misunderstanding something.

All in all: keep doing what’s best/customary to keep track of things; now I know that such things can happen and that it’s not an issue (on my side, at least). :)