On Thu, 2017-06-01 at 10:18 +0200, intrigeri wrote:
> hi!
>
> anonym:
> > intrigeri:
> > > I'll make the call as the 3.0 release manager if no consensus
> > > emerges,
>
> After re-reading this discussion, it appears that the only people
> substantially affected by this decision (apart of Tails
hi!
anonym:
> intrigeri:
>> I'll make the call as the 3.0 release manager if no consensus
>> emerges,
After re-reading this discussion, it appears that the only people
substantially affected by this decision (apart of Tails users of
course) will be myself and our usual manual testers. So I'll
intrigeri:
> Hi,
>
> ni...@thykier.net:
>> Release date
>>
>
>> We plan to release on 2017-06-17.
>
>> […]
>
> Yeah! I'm relieved this is now public info and we don't have to
> discuss our plans privately within a tiny Tails release managers
> cabal anymore.
>
> So, what should
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
intrigeri:
> ni...@thykier.net:
>> Release date
>>
>
>> We plan to release on 2017-06-17.
>
>> […]
>
> Yeah! I'm relieved this is now public info and we don't have to
> discuss our plans privately within a tiny Tails release managers
> cabal anymore.
>
> So, what should we do
Hi,
ni...@thykier.net:
> Release date
>
> We plan to release on 2017-06-17.
> […]
Yeah! I'm relieved this is now public info and we don't have to
discuss our plans privately within a tiny Tails release managers
cabal anymore.
So, what should we do about it? I'll make the call as
