Autor: intrigeri Data: A: The Tails public development discussion list Assumpte: Re: [Tails-dev] Release schedule for 2018
Hi,
sajolida: > intrigeri:
>> Should I explicitly point everyone affected off-list to this thread? > That would be cool! Now, I could understand if you think that it's not
> part of your job or forget about it. >> Or rely on team managers to do so?
> Sounds more like their responsibility but I don't remember them
> commenting on these changes neither this time...
I'm adding this to the Foundations Team's role page:
* proposing a release schedule for next year once Mozilla's own
schedule is available (generally during Q3), ensuring everyone
affected is aware of it and OK with it (e.g. team managers for
sponsor deliverables), leading this discussion to a conclusion,
updating the [[contribute/calendar]] accordingly, and asking
<tails-rm@???> to decide between themselves how they will share
the [[roles/release_manager]] shifts;
Meta: usually I'd rather see a more formal process for editing Core
work definitions, but in this case it's obvious that this work
absolutely has to be done (⇒ part of Core work) and I don't see which
other team/role would realistically handle it. If my bypassing of due
process is problematic, please let me know.