Hi, anonym wrote (10 Apr 2012 18:43:15 GMT) : > I just want to emphasize that since tails-greeter and persistence > finally is here we really should finish all the things that > essentially have been in a "wait until tails-greeter/persistence is > done"-state. Some of these are rather trivial [1] but some are (at > least potentially) a bit more involved [2]. Personally I'd like to > see a relatively early > 0.12 with as many of these bits and pieces in place as possible.
Maybe we should focus on this 0.12 first, and move my proposal to post-0.12? Doing this would both speed up 0.12 release, and allow us to collectively focus on similar topics both in the 0.11..0.12 times, and in post-0.12 ones, instead of spreading our energies around. However, working on such a 0.12 release now, given the Wheezy freeze expected date (June) would draw much of the energies that we could have put into building and testing upon live-build 3.x and Wheezy before the freeze. To my eyes, this is a major drawback of such a rescheduling. Alternatively, if we focus on the infrastructure and surroundings at post-0.11 time, we can set a deadline to mid-June, probably most of the work will be done by then, and then 0.12 could happen end of July. Is 0.11 + 3months early enough? I think it is. >> * Tor 0.2.3.x >> We need to make sure the next major Tor stable release will be great >> for Tails, with a focus on the separate streams features. >> Next steps: everyone of us, let's run Tor 0.2.3.x and use the >> separate streams feature. Put it into Tails experimental. > For the record I've run 0.2.3 since january, and several Isolate* > options for a month, without any noticeable issues. Same here. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc _______________________________________________ tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev
