Hi,
since we now build our own web browser, I propose we switch to our
"ideal" documented release schedule [1] for the release after 0.14.
This would mean:
* November 6th: freeze and RC1
* November 20th: Firefox ESR is out
* November 22th: RC2
* November 27th: Tails release
If we do so, given the little time until freeze, and the little new
stuff we have ready in devel / experimental, that would be a minor
release (bugfix-only or not, called 0.14.1 or 0.15, remains to be
discussed), which, if you ask me, is good, and will hopefully give us
more time for infrastructure (lizard, tests) and future (Wheezy,
live-build 3.x, etc.) work.
Side note #1: sticking to this schedule probably means sometimes
importing iceweasel updated source from the Debian source package into
Git ourselves, rather than from Mike Homey's Vcs-Git, as this
repository often lags behind.
Side note #2: given 0.13 ships with an outdated signing key, it is no
good test-bed for incremental updates, but I do think 0.14 will be,
and I do hope we can ship late-November-Tails with incremental updates
enabled by default!
[1]
https://tails.boum.org/contribute/release_schedule/
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
