Hi! intrigeri: > ni...@thykier.net: >> Release date >> ============ > >> We plan to release on 2017-06-17. > > I see two options: > > A. Coordinate Tails 3.0 and Debian Stretch releases > > We can prepare two releases at the same time: 2.12.1 and 3.0. > Both should be ready (including release notes, uploading ISO, > manual testing) on June 13. But on June 13 we release 2.12.1 only > (we have to release _something_ on that day anyway due to the > Firefox security updates), and we wait until June 17 to publish > Tails 3.0, at the same time as Debian Stretch. > > B. Don't bother and proceed as our calendar says > > I.e. simply release Tails 3.0 on June 13. > > Pros and cons: > > - Option A costs us one more "Emergency releases" i.e. 2.25 days > of work (release management + manual testing). > > - Option A forces us to integrate Tor Browser 7.0 into Tails 2.x: > this work has been based on the Tails 3.x codebase so far. I don't > know if rebasing it onto the stable branch would be trivial, or > a lot of work. anonym, what's your feeling? > > - Option B is less work, therefore it increases the chances that we > manage to make 3.0 build reproducibly, which gives us good > communication opportunities. So: > > * Ulrike (who committed to handle such communication) and sajolida > (who'll likely be needed to review it), do you think you can > realistically take advantage of this opportunity?
I think option B being less work in general, for all of us, so IMO we should go this way instead. I can absolutely take the time to prepare communication next week so that sajolida would have enough time to review it. Cheers! u. _______________________________________________ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
