Re: [Tails-dev] After Tails 0.11 - a vision

Delete this message

Reply to this message
Autor: alan
Data:  
A: tails-dev
Assumptes nous: Re: [Tails-dev] tails-greeter feature/refactor_languages [Was: After Tails 0.11 - a vision]
Assumpte: Re: [Tails-dev] After Tails 0.11 - a vision

Hi,

intrigeri:
> it's likely much of April will be spent on polishing and releasing
> Tails 0.11.
>
> Once this is done, we will have shipped a few major new features into
> the wild. Once this is done, I hereby propose we pause implementation
> of big new features for a short while, and instead focus on two areas
> where, I think, we are lagging behind:
>
> * re-scaling our _infrastructure_
> * connecting back to our immediate _surroundings_
>


I agree that focusing on that would be important in the near future.
Regarding my personnal implication, I don't promise I will do more that
testing for it to happen.

However, I also share anonym's concern of a quick-enough 0.12 to bring
features that are really close, thanks to the work done for 0.11.

intrigeri:
> anonym:
> >> 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.
>
> > Perhaps. A compromise would be to get the more or less trivial ones
> > (i.e. the tails-greeter controls for windows camouflage etc.) out
> > quickly in the first point-release, which I don't expect to suck up
> > much energy (they seem like good procrastination targets to me :)).
>
> I can live with this compromise, but the result should not be called
> a point-release IMHO: instead, it would be a tiny 0.12, that would be
> out quickly with only a few new features.
>

I don't know how quick I would like to see this tiny 0.12. Perhaps july
is soon enough.

> Also, doing so implies being extra careful when working on
> tails-greeter (or switch to stable/testing/devel branches there too):
> if we go this way, only stuff that is fit for a quick release should
> be merged into tails-greeter master. Longer-term work shall happen in
> topic branches.
>

If some of you plan to work on tails-greeter, please consider I expect
future tails-greeter to be based on feature/refactor_languages branch,
that not merged as is currently still introducing a bug (tails-greeter
UI not in english after restarting gdm3 with a running non-english Tails
session.

Cheers


--