Re: 8.1 (and maybe 7.9) planning

2015-05-25 Thread Joerg Jaspert
On 13951 March 1977, Adam D. Barratt wrote: Based on received responses and the current date, I'm proposing June 6th for 8.1 (and then looking at other dates for 7.9). Does that still work for people? Sounds ok to me. Start at 10 UTC or earlier/later? I was assuming either 8ish UTC

Re: 8.1 (and maybe 7.9) planning

2015-05-24 Thread Paul Wise
On Sat, 2015-05-23 at 16:27 +0100, Adam D. Barratt wrote: press@ - ping? :-) ... Based on received responses and the current date, I'm proposing June 6th for 8.1 (and then looking at other dates for 7.9). Does that still work for people? I can be available as a backup for Neil if needed.

Re: 8.1 (and maybe 7.9) planning

2015-05-24 Thread Adam D. Barratt
On Thu, 2015-05-21 at 09:56 +0200, Joerg Jaspert wrote: On 13947 March 1977, Adam D. Barratt wrote: As seems to have become the norm, now that Jessie's out it's time to start planning for the first point release. We're also a little overdue for 7.9 as Jessie work took precedence; 7.9

Re: 8.1 (and maybe 7.9) planning

2015-05-23 Thread Adam D. Barratt
press@ - ping? :-) On Wed, 2015-05-20 at 21:22 +0100, Adam D. Barratt wrote: On Fri, 2015-05-01 at 11:17 +0100, Adam D. Barratt wrote: [Added some missed CCs; sigh] On 2015-04-30 22:16, Adam D. Barratt wrote: Hi, As seems to have become the norm, now that Jessie's out it's time

Re: 8.1 (and maybe 7.9) planning

2015-05-21 Thread Steve McIntyre
On Wed, May 20, 2015 at 09:22:44PM +0100, Adam Barratt wrote: On Fri, 2015-05-01 at 11:17 +0100, Adam D. Barratt wrote: [Added some missed CCs; sigh] On 2015-04-30 22:16, Adam D. Barratt wrote: Hi, As seems to have become the norm, now that Jessie's out it's time to start planning for

Re: 8.1 (and maybe 7.9) planning

2015-05-21 Thread Joerg Jaspert
On 13947 March 1977, Adam D. Barratt wrote: As seems to have become the norm, now that Jessie's out it's time to start planning for the first point release. We're also a little overdue for 7.9 as Jessie work took precedence; 7.9 really wants to take place after 8.1, as we have some

Re: 8.1 (and maybe 7.9) planning

2015-05-20 Thread Cyril Brulebois
Adam D. Barratt a...@adam-barratt.org.uk (2015-05-20): Based on received responses and the current date, I'm proposing June 6th for 8.1 (and then looking at other dates for 7.9). Does that still work for people? Provided the p-u freeze happens on time so that I can perform d-i tests ahead of

Re: 8.1 (and maybe 7.9) planning

2015-05-20 Thread Adam D. Barratt
On Fri, 2015-05-01 at 11:17 +0100, Adam D. Barratt wrote: [Added some missed CCs; sigh] On 2015-04-30 22:16, Adam D. Barratt wrote: Hi, As seems to have become the norm, now that Jessie's out it's time to start planning for the first point release. We're also a little overdue for

Re: 8.1 (and maybe 7.9) planning

2015-05-01 Thread Adam D. Barratt
[Added some missed CCs; sigh] On 2015-04-30 22:16, Adam D. Barratt wrote: Hi, As seems to have become the norm, now that Jessie's out it's time to start planning for the first point release. We're also a little overdue for 7.9 as Jessie work took precedence; 7.9 really wants to take place

Re: 8.1 (and maybe 7.9) planning

2015-05-01 Thread Neil McGovern
On Fri, May 01, 2015 at 12:08:59PM +0200, Cyril Brulebois wrote: May 23/24 Offline-ish on May 23. Same for me. May 30/31 OK. OK June 6/7 Offline on June 6, offline-ish on June 7. OK June 13/14 Offline-ish on June 13. OK June 20/21 OK. Offline-ish both

Re: 8.1 (and maybe 7.9) planning

2015-05-01 Thread Cyril Brulebois
(cc+=boot) Adam D. Barratt a...@adam-barratt.org.uk (2015-04-30): As seems to have become the norm, now that Jessie's out it's time to start planning for the first point release. AFAICT there haven't been too many reports of d-i being badly broken, so there's not much to be fixed. Here's a

Re: 8.1 (and maybe 7.9) planning

2015-05-01 Thread Stefan Lippers-Hollmann
Hi On 2015-05-01, Cyril Brulebois wrote: [...] - I see gnutls28, linux, and wpa in pu; some testing couldn't hurt. wpa should be safe (famous last words), as it contains only the one-line security fix for CVE-2015-1863[1], which applies to a code path/ file not used by the udeb (as CONFIG_P2P