Re: [Tails-dev] Release schedule for 2018

Delete this message

Reply to this message
Autore: anonym
Data:  
To: The Tails public development discussion list
Oggetto: Re: [Tails-dev] Release schedule for 2018
intrigeri:
> Hi,
>
> this time of the year again! Mozilla published their release schedule
> for 2018, so we can now decide which releases will be major, and which
> ones will be bugfix-only. Once this is done our release managers will
> organize their shifts.


Thanks for taking the initiative for this!

> Proposal:
>
> * 2017-09-26: Release 3.2 (Firefox 52.4) — anonym is the RM
>
>     Major release.

>
> * 2017-11-14: Release 3.3 (Firefox 52.5)
>
>     Bugfix release.

>
> * 2018-01-16: Release 3.4 (Firefox 52.6)
>
>     Bugfix release: yes, the second in a row. Rationale: reset the
>     major/bugfix cycle so that the June release can be a major one,
>     take December holiday into account, and free some time to work on
>     major sponsor deliverables & other roadmap goals.


Ack, I very much agree with this.

> * 2018-03-06: Release x.y (Firefox 52.7)
>
>     Major release (possibly the first Buster-based Tails).

>
> * 2018-05-01: Release x.y (Firefox 52.8)
>
>     Bugfix release.

>
> * 2018-06-26: Release x.y (Firefox 59.2)
>
>     Major release: we're switching to a major new version of Firefox
>     + let's deliver our pre-summer work to users.

>
> * 2018-08-21: Release x.y (Firefox 59.3)
>
>     Bugfix release: doing 2 major releases in a row is too much work,
>     especially during Northern hemisphere summer.

>
>     But this is the last release before the end of our contract with
>     SponsorW! So either SponsorW work is fully completed in time for
>     the June 26 release, or we'll have to put out a beta version in
>     August, that includes the final version of that work, which will
>     be released in stable Tails in October.


So much for the "let's try to avoid having grant deadlines around the end of summer" attempt... :) [Note: this is not a real disappointment, just ] If the beta workaround is cool, this sounds perfect.

> * 2018-10-16: Release x.y (Firefox 59.4)
>
>     Major release.

>
> * 2018-11-27: Release x.y (Firefox 59.5)
>
>     Bugfix release.

>
> Thoughts?


LGTM!

Cheers!