Tails

#2 Updated by anonym 2014-10-08 07:49:38

A discussion for the coordination of Tails 1.2 vs TBB 4.0 was started here: https://lists.torproject.org/pipermail/tbb-dev/2014-October/000134.html

The discussion for how to do this in general hasn’t started yet.

#5 Updated by anonym 2014-11-12 16:06:49

A discussion has started for how we can do this in general: https://lists.torproject.org/pipermail/tbb-dev/2014-October/000143.html

I guess it boils down to: “We hope the TBB we intend to ship is available around 18:00 CEST the day (Monday) before the Tails release (Tuesday).” While I could document this vague “strategy”, I think there is little point in doing so before we know how it works out for a couple of releases, like 1.2.1 and 1.2.2.

#6 Updated by intrigeri 2014-11-12 17:41:13

> I guess it boils down to: “We hope the TBB we intend to ship is
> available around 18:00 CEST the day (Monday) before the Tails
> release (Tuesday).”

I think “hoping” is not always good enough to coordinate things on our side, particularly our QA process: explicitly asking them (IRC works fine for this kind of things, in my experience) how things are going, and what their ETA is, e.g. on Friday or during the week-end, will probably help reschedule our QA and release process (if needs be) without waiting for Monday 6pm to realize that everything will be late and testers suddenly have to forget about their plans for Wednesday or something.

> While I could document this vague “strategy”, I think there is
> little point in doing so before we know how it works out for
> a couple of releases, like 1.2.1 and 1.2.2.

Agreed.

#7 Updated by anonym 2014-12-01 10:29:53

intrigeri wrote:
> > I guess it boils down to: “We hope the TBB we intend to ship is
> > available around 18:00 CEST the day (Monday) before the Tails
> > release (Tuesday).”
>
> I think “hoping” is not always good enough to coordinate things on our side, particularly our QA process: explicitly asking them (IRC works fine for this kind of things, in my experience) how things are going, and what their ETA is, e.g. on Friday or during the week-end, will probably help reschedule our QA and release process (if needs be) without waiting for Monday 6pm to realize that everything will be late and testers suddenly have to forget about their plans for Wednesday or something.

Of course, but we still have to do some hoping when we write the release schedule. :)

> > While I could document this vague “strategy”, I think there is
> > little point in doing so before we know how it works out for
> > a couple of releases, like 1.2.1 and 1.2.2.
>
> Agreed.

Ok, moving this to the 1.3 milestone then.

One thing to add to this strategy I think is to always try to plan for a one-day delay, so testers availability should be asked for both the Tuesday and Wednesday around the ESR release date. This was done for the 1.2.1 release already.

#9 Updated by intrigeri 2014-12-01 10:51:27

> One thing to add to this strategy I think is to always try to plan for a one-day
> delay, so testers availability should be asked for both the Tuesday and Wednesday
> around the ESR release date.

ACK.