23/10/12 22:20, anonym wrote:
> 23/10/12 21:02, intrigeri wrote:
>> anonym wrote (23 Oct 2012 18:47:26 GMT) :
>>> Agreed. I think we may need a completely different release schedule
>>> than what we have now, which is:
>>
>>> October 25th: release of RC2.
>>> October 30th: release of 0.14.
>>
>>> Clearly this won't work if we do something drastic, which seems
>>> necessary. What about we bump RC2 until we have a fix for this
>>> (perhaps we should set a latest date?), and then release the final
>>> Tails 0.14 a week after that. That gives a few extra days for RC
>>> testers to find new issues with whatever solution we picked.
>>
>> Thanks for raising this topic. This proposal suits me well.
>>
>> FYI, on the iceweasel+torbrowser side of things, my plan is to
>> (hopefully) put a first test ISO out at some point before Thursday
>> 25th at noon CEST. Things are going well, and I think this is doable.
>> I'd like some of us (and as many people as possible, actually!) to
>> review and test it for a few days before we merge it and call that
>> RC2. So, I think best case is RC2 on Monday, 29th.
This is today.
>> Given another test
>> ISO will have been out for a few days already, we might dare releasing
>> 0.14 a bit less than a full week later. I'm happy to let this decision
>> up to whoever will actually do the release.
>
> That would be me, and I'm ok with making such a decision.
I have merged feature/torbrowser into testing, so it'll en up in rc2.
However, esr10 is out:
http://packages.qa.debian.org/i/iceweasel/news/20121026T165314Z.html
So, what should we do? I think it's clear that we need to rebase our
Iceweasel on esr10 for the final release of Tails 0.14. But do we want
it in rc2 too? After all one of the purposes to ship an rc2 was to test
the new Iceweasel. Because of that I'm leaning towards delaying rc2 a
few days if we can have an updated package built and uploaded within
that period.
Cheers!
