On 02/21/2017 11:39 PM, Steve McIntyre wrote: > On Fri, Feb 17, 2017 at 05:23:16PM +0100, Emmanuel Kasper wrote: >>>> Another thing I've been considering is that we intend the official cloud >>>> images to be ready and released at the same time as the primary stretch >>>> announcement. (Well, I intend this anyway, and am assuming that the rest >>>> of the cloud team has no major objections.) Ideally the release >>>> announcement will at least make mention of the availability of cloud >>>> images for whichever platforms are ready at release time (AWS, MS Azure, >>>> Google, Docker, etc). What's the best way to ensure that this happens? >>>> Should we try to come up with the appropriate wording and pass it along >>>> to press@? Is that going to reach the right people? >>> >>> That's a good start, yes. :-) >>> >>> I'm expecting to get Stretch Openstack images built on release >>> day. What other images can we expect to get done then? >> >> I can push vagrant images on that same day. >> Starting from the momment the release iso is available somwhere online >> with its checksum I need two hours to build the image locally and upload >> to the Vagrant cloud servers (mostly upload time) > > Cool. We'll have test amd64 images ready to play with comparatively > early on release day, and we'll be testing them. I'll be live in > #debian-cd and can coordinate there...
OK. I supposed planned release day will be announce on the debian-cd mailing list, like for the stable point releases ?
