Re: [Tails-dev] Upcoming release schedule plan
On 03/09/12 18:51, anonym wrote: > berta...@ptitcanardnoir.org: >> Hi, >> >> Following our discussions on the timeline for the next release, here is >> the plan we ended up with and I committed to send on this list : >> >> - Theoritically: ESR (August 28th) + 1 week = September 4th >> - August 23: release 0.13~rc1, do the test suite together >> - Week 35 >> - Mon 27th: ESR is out >> update of the GnuPG docs >> - Week 36 >> - Tue 4th: release 0.13~rc2, testing phase > > At this point we should've had the Iceweasel ESR, but nowadays Mike > Hommey seems to only upload to the official backports instead of > mozilla.debian.net, so it won't go live until it hits testing (remember, > there's a 10 day delay for unstable --> testing). The end result is that > we will have the ESR no earlier than the 9th of September (and hopefully > no later so we can spend 10-11th running the test suite). I fear I won't be able to help you out with the testing once again. That sucks :( signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Upcoming release schedule plan
berta...@ptitcanardnoir.org: > Hi, > > Following our discussions on the timeline for the next release, here is > the plan we ended up with and I committed to send on this list : > > - Theoritically: ESR (August 28th) + 1 week = September 4th > - August 23: release 0.13~rc1, do the test suite together > - Week 35 > - Mon 27th: ESR is out > update of the GnuPG docs > - Week 36 > - Tue 4th: release 0.13~rc2, testing phase At this point we should've had the Iceweasel ESR, but nowadays Mike Hommey seems to only upload to the official backports instead of mozilla.debian.net, so it won't go live until it hits testing (remember, there's a 10 day delay for unstable --> testing). The end result is that we will have the ESR no earlier than the 9th of September (and hopefully no later so we can spend 10-11th running the test suite). Because of this, and that not a single other package has been updated since ~rc1, some of us seemed to think that an ~rc2 would be a waste of time. Looking at the recent changes in the testing branch also supports that: $ git log --abbrev-commit --pretty=oneline 0.13-rc1..testing 6d7395d Import live-config and live-config-sysvinit 3.0.3-1. 406ecac Rewrite the changelog for 0.13~rc1 in a more digest form 2faaa6b Enable the ikiwiki trail plugin for the locally built wiki too. (+ another not-yet pushed commit that updates the deb.tp.o signing key, which expired today) At first glance 6d7395d may look like something, but actually it just makes sure that we pin the versions of live-config* we already shipped in ~rc1. Given all this, unless someone strongly objects, I will skip preparing/uploading/announcing ~rc2 and work on something more productive tomorrow. Cheers! signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Upcoming release schedule plan
On Sat, Aug 25, 2012 at 03:01:51PM +0200, berta...@ptitcanardnoir.org wrote: > Following our discussions on the timeline for the next release, here is > the plan we ended up with and I committed to send on this list : > > - Theoritically: ESR (August 28th) + 1 week = September 4th > - August 23: release 0.13~rc1, do the test suite together Insert a "call for translation updates". > - Week 35 > - Mon 27th: ESR is out > update of the GnuPG docs > - Week 36 > - Tue 4th: release 0.13~rc2, testing phase Insert a "call for translation quality assurance and minor fixes". > - Thu 6th: monthly meeting > - Week 37 > - Tue 11th: release 0.13 (final) Please remember that the test suite needs to be done before pushing the final image. -- Ague pgpFQQD9e93Ho.pgp Description: PGP signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
