[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Q to both: release date



Hi lucas,

On 2017-04-05 09:17, Lucas Nussbaum wrote:
How is the release process doing?

As noted by Chris too, the Release Team has all the details and can reply on this specific question. I've pinged them about issuing a status update
on the freeze and proposed my help write/review the mail.

Looking at the numbers, the Release Team is doing quite well (as always). They seem to be able to process unblock requests quite quickly. Kudos for
the Release Team!

Last update from a member of the team dates back to February:
https://nthykier.wordpress.com/2017/02/04/the-stretch-freeze-is-coming/

Since then, some blockers were resolved (stretch-backports area created,
gcc-5 removal done, openssl transition (mostly)).

Release Managers are keeping a checklist up-to-date on:

https://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList/StretchCheckList

We've had a 2nd release candidate of the installer.

So, globally, it looks like it is going okay. I think that the Release
Team can be helped with more rc-bug squashers. There are also some BSPs coming
soon. So I guess it would help to deal with a few issues.

What is your guesstimate for the release date?

“When it's ready!“, of course :-)

I am sure members of the release team (and especially release managers)
have an idea of which date (or period of time) to target for the release
date. They didn't disclose it. So I do not see a reason to do so on my
side. It would counter-productive and would send a bad message to people
following this mailing-list (as it could be taken as an announcement, no
matter the size of the warnings you could put in the mail).

I trust the Release Team to do a stellar job at handling this freeze
cycle, as always.

If you were asked that in a press interview, is there
something that you would like to stress about the release process or the
upcoming release?


Testing, Squashing RC Bugs, Reporting issues early.

--
Mehdi


Reply to: