Re: Scheduling 9.5

[Adam D. Barratt]

On Tue, 2018-06-12 at 18:00 +0200, Laura Arjona Reina wrote:
> 
> El 12 de junio de 2018 13:44:52 CEST, "Adam D. Barratt"  rratt.org.uk> escribió:
[...]
> > - July 7th
> 
> This we (publicity) can, and prefer it.
> 
> > - July 14th
> 
> This, could be possible, but only one of us is available.

After some discussion on IRC, we've decided to go with the 14th and
look at making the press side more handleable for that date.

Regards,

Adam

Re: Scheduling 9.5

[Ansgar Burchardt]

Hi,

On Sat, 2018-06-23 at 17:30 +0100, Adam D. Barratt wrote:
> On Tue, 2018-06-12 at 12:44 +0100, Adam D. Barratt wrote:
> [...]
> > Given all of the above, I think the sanest option is to concentrate
> > on getting 8.11 done and jessie off our radar and then get 9.5
> > sorted.
> > 
> > For suggested dates for 9.5, we know that June 30th is a no-go,
> > Debcamp starts on July 21st and then Debconf on the 28th. So that
> > leaves us with:
> > 
> > - July 7th
> > - July 14th
> > 
> > Are people available for either or both of those dates?
> 
> The 7th is looking like the favourite so far (although would mean
> freezing next weekend), but we still need an ftp-master (N)ACK on
> either / both date.

I still have time on either weekend.

Ansgar

Re: Scheduling 9.5

[Joerg Jaspert]

On 15077 March 1977, Adam D. Barratt wrote:
>> - July 7th
>> - July 14th
>> Are people available for either or both of those dates?
> The 7th is looking like the favourite so far (although would mean
> freezing next weekend), but we still need an ftp-master (N)ACK on
> either / both date.

No way for me for both, sorry.

-- 
bye, Joerg

Re: Scheduling 9.5

[Adam D. Barratt]

On Tue, 2018-06-12 at 12:44 +0100, Adam D. Barratt wrote:
[...]
> Given all of the above, I think the sanest option is to concentrate
> on getting 8.11 done and jessie off our radar and then get 9.5
> sorted.
> 
> For suggested dates for 9.5, we know that June 30th is a no-go,
> Debcamp starts on July 21st and then Debconf on the 28th. So that
> leaves us with:
> 
> - July 7th
> - July 14th
> 
> Are people available for either or both of those dates?

The 7th is looking like the favourite so far (although would mean
freezing next weekend), but we still need an ftp-master (N)ACK on
either / both date.

Adam

Re: Scheduling 9.5

[Cyril Brulebois]

Adam D. Barratt  (2018-06-12):
> Given all of the above, I think the sanest option is to concentrate on
> getting 8.11 done and jessie off our radar and then get 9.5 sorted.
> 
> For suggested dates for 9.5, we know that June 30th is a no-go, Debcamp
> starts on July 21st and then Debconf on the 28th. So that leaves us with:
> 
> - July 7th
> - July 14th
> 
> Are people available for either or both of those dates?

Will try hard to be available for the timing of your choosing.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Scheduling 9.5

[Laura Arjona Reina]

El 12 de junio de 2018 13:44:52 CEST, "Adam D. Barratt" 
 escribió:
>On 2018-06-08 18:51, Adam D. Barratt wrote:
>> [Cc += debian-kernel]
>> 
>> On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
>>> On 15037 March 1977, Jonathan Wiltshire wrote:
>[...]
>> We're past any of the above by now, and while looking through the
>to-do
>> list for the final jessie point release, I noticed that we currently
>> have some packages in opu with versions higher than stable.
>> 
>> We can either accept the packages and put up with the situation for a
>> short while, or do 9.5 before 8.11. In practical terms, that would
>> likely mean both 9.5 and 8.11 on June 23rd, freezing both next
>weekend.
>> How do people feel about that?
>
>After discussions on IRC, it appears unlikely that the currently WIP 
>kernel update will be ready in sufficient time to be happy with it on 
>all architectures.
>
>So the possible options are:
>
>- go ahead with freezing 9.5 this weekend, and hope the kernel's ready 
>in time
>- go ahead with freezing 9.5 this weekend, and update the kernel via 
>stable-updates later
>- just do 8.11 this weekend, accept the version skew and get 9.5 
>released as soon as we can
>
>To be entirely honest, I'm not that comfortable with announcing a
>freeze 
>this close to the actual date. In terms of packages with version skew, 
>we have:
>
>- packages from the security archive, where users upgrading should 
>already have the jessie-security package installed in any case
>- intel-microcode, src:patch and clamav, where it looks like the jessie
>
>package should work on stretch without issues
>- tzdata, which is already available from stretch-updates.
>
>Given all of the above, I think the sanest option is to concentrate on 
>getting 8.11 done and jessie off our radar and then get 9.5 sorted.
>
>For suggested dates for 9.5, we know that June 30th is a no-go, Debcamp
>
>starts on July 21st and then Debconf on the 28th. So that leaves us 
>with:
>
>- July 7th

This we (publicity) can, and prefer it.

>- July 14th

This, could be possible, but only one of us is available.

Cheers
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Sent with K-9 mail

Re: Scheduling 9.5

[Steve McIntyre]

On Tue, Jun 12, 2018 at 12:44:52PM +0100, Adam Barratt wrote:
>On 2018-06-08 18:51, Adam D. Barratt wrote:
>
>Given all of the above, I think the sanest option is to concentrate on
>getting 8.11 done and jessie off our radar and then get 9.5 sorted.
>
>For suggested dates for 9.5, we know that June 30th is a no-go, Debcamp
>starts on July 21st and then Debconf on the 28th. So that leaves us with:
>
>- July 7th
>- July 14th
>
>Are people available for either or both of those dates?

Both look good for me, yup.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Yes, of course duct tape works in a near-vacuum. Duct tape works
 anywhere. Duct tape is magic and should be worshipped."
   -― Andy Weir, "The Martian"

Re: Scheduling 9.5

[Adam D. Barratt]

On 2018-06-08 18:51, Adam D. Barratt wrote:

[Cc += debian-kernel]

On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:

On 15037 March 1977, Jonathan Wiltshire wrote:

[...]

We're past any of the above by now, and while looking through the to-do
list for the final jessie point release, I noticed that we currently
have some packages in opu with versions higher than stable.

We can either accept the packages and put up with the situation for a
short while, or do 9.5 before 8.11. In practical terms, that would
likely mean both 9.5 and 8.11 on June 23rd, freezing both next weekend.
How do people feel about that?


After discussions on IRC, it appears unlikely that the currently WIP 
kernel update will be ready in sufficient time to be happy with it on 
all architectures.


So the possible options are:

- go ahead with freezing 9.5 this weekend, and hope the kernel's ready 
in time
- go ahead with freezing 9.5 this weekend, and update the kernel via 
stable-updates later
- just do 8.11 this weekend, accept the version skew and get 9.5 
released as soon as we can


To be entirely honest, I'm not that comfortable with announcing a freeze 
this close to the actual date. In terms of packages with version skew, 
we have:


- packages from the security archive, where users upgrading should 
already have the jessie-security package installed in any case
- intel-microcode, src:patch and clamav, where it looks like the jessie 
package should work on stretch without issues

- tzdata, which is already available from stretch-updates.

Given all of the above, I think the sanest option is to concentrate on 
getting 8.11 done and jessie off our radar and then get 9.5 sorted.


For suggested dates for 9.5, we know that June 30th is a no-go, Debcamp 
starts on July 21st and then Debconf on the 28th. So that leaves us 
with:


- July 7th
- July 14th

Are people available for either or both of those dates?

Regards,

Adam

Re: Scheduling 9.5

[Adam D. Barratt]

-kernel: any chance of a yes/no ASAP, please?

On 2018-06-08 18:51, Adam D. Barratt wrote:

[Cc += debian-kernel]

On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:

On 15037 March 1977, Jonathan Wiltshire wrote:
>  - May 26th (meaning freeze this coming weekend, which might be a
> big
>  ask)

No.

>  - Jun 2nd (which may require an unusual SRM)

Possible.

>  - Jun 9th (getting quite a way out of cadence, but maybe that
> can't be
>    helped)

Possible.


We're past any of the above by now, and while looking through the to-do
list for the final jessie point release, I noticed that we currently
have some packages in opu with versions higher than stable.

We can either accept the packages and put up with the situation for a
short while, or do 9.5 before 8.11. In practical terms, that would
likely mean both 9.5 and 8.11 on June 23rd, freezing both next weekend.
How do people feel about that?


Unless we can get a definite answer r.e. the kernel very quickly, we 
might have to live with the version skew for a short while and arrange 
alternate dates for 9.5, which would then be in July (as the 30th won't 
work for either Sledge or I, at least), which would be well past our 
2-month goal.


Regards,

Adam

Re: Scheduling 9.5

[Ansgar Burchardt]

On Fri, 2018-06-08 at 18:51 +0100, Adam D. Barratt wrote:
> We can either accept the packages and put up with the situation for a
> short while, or do 9.5 before 8.11. In practical terms, that would
> likely mean both 9.5 and 8.11 on June 23rd, freezing both next
> weekend.

Should be fine with me; Joerg wanted to do the 8.11 one, but if he has
time restrictions on June 23rd and doing 8.11 after 9.5 would be too
late for him, I could probably also do both.

(If Joerg wants to do both, that's also fine with me.)

Ansgar

Re: Scheduling 9.5

[Laura Arjona Reina]

El 8 de junio de 2018 19:51:18 CEST, "Adam D. Barratt" 
 escribió:
>[Cc += debian-kernel]
>
>On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
>> On 15037 March 1977, Jonathan Wiltshire wrote:
>> >  - May 26th (meaning freeze this coming weekend, which might be a
>> > big
>> >  ask)
>> 
>> No.
>> 
>> >  - Jun 2nd (which may require an unusual SRM)
>> 
>> Possible.
>> 
>> >  - Jun 9th (getting quite a way out of cadence, but maybe that
>> > can't be
>> >    helped)
>> 
>> Possible.
>
>We're past any of the above by now, and while looking through the to-do
>
>list for the final jessie point release, I noticed that we currently
>have some packages in opu with versions higher than stable.
>
>We can either accept the packages and put up with the situation for a
>short while, or do 9.5 before 8.11. In practical terms, that would
>likely mean both 9.5 and 8.11 on June 23rd, freezing both next weekend.
>How do people feel about that?
>

Ok for publicity.

Cheers

-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
Sent with K-9 mail

Re: Scheduling 9.5

[Steve McIntyre]

On Fri, Jun 08, 2018 at 06:51:18PM +0100, Adam Barratt wrote:
>[Cc += debian-kernel]
>
>On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
>> On 15037 March 1977, Jonathan Wiltshire wrote:
>> >  - May 26th (meaning freeze this coming weekend, which might be a
>> > big
>> >  ask)
>> 
>> No.
>> 
>> >  - Jun 2nd (which may require an unusual SRM)
>> 
>> Possible.
>> 
>> >  - Jun 9th (getting quite a way out of cadence, but maybe that
>> > can't be
>> >    helped)
>> 
>> Possible.
>
>We're past any of the above by now, and while looking through the to-do 
>list for the final jessie point release, I noticed that we currently
>have some packages in opu with versions higher than stable.
>
>We can either accept the packages and put up with the situation for a
>short while, or do 9.5 before 8.11. In practical terms, that would
>likely mean both 9.5 and 8.11 on June 23rd, freezing both next weekend.
>How do people feel about that?

That works ok for me.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"This dress doesn't reverse." -- Alden Spiess

Re: Scheduling 9.5

[Adam D. Barratt]

[Cc += debian-kernel]

On Sun, 2018-05-20 at 12:04 +0200, Joerg Jaspert wrote:
> On 15037 March 1977, Jonathan Wiltshire wrote:
> >  - May 26th (meaning freeze this coming weekend, which might be a
> > big
> >  ask)
> 
> No.
> 
> >  - Jun 2nd (which may require an unusual SRM)
> 
> Possible.
> 
> >  - Jun 9th (getting quite a way out of cadence, but maybe that
> > can't be
> >    helped)
> 
> Possible.

We're past any of the above by now, and while looking through the to-do 
list for the final jessie point release, I noticed that we currently
have some packages in opu with versions higher than stable.

We can either accept the packages and put up with the situation for a
short while, or do 9.5 before 8.11. In practical terms, that would
likely mean both 9.5 and 8.11 on June 23rd, freezing both next weekend.
How do people feel about that?

Cheers,

Adam

Re: Scheduling 9.5

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, 2018-06-05 at 15:44 +0200, Cyril Brulebois wrote:
> > Context: https://salsa.debian.org/kernel-team/linux/merge_requests/30
> 
> Many thanks for the heads-up. I'll be on the lookout for a possible
> late ABI bump then. Feel free to poke me when that gets accepted into
> p-u so that I can adjust our git branch and perform a few build and
> runtime tests.

This is now up to 4.9.106 and there will definitely be an ABI break. I missed
the thread start (I'm not subscribed to -release anymore), but in the quoted
text I can see there were three proposed dates for the 9.5 point release. May
26th and June 2nd are out of the equation now but is June 9th already
targeted?

If so, we really need to move forward on this (and it might be a bit late
already) if we want to make sure it builds everywhere.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlsWuPEACgkQ3rYcyPpX
RFs/qgf/QnAItR/yQtgU9bl7ab4YGSaKgeW98dVeray761S6G0hQVJRF4UvqsUk4
/ZWj2jsZbMFviGD0WbKHncsRzaY0rj9aRk19LPpSpyDLbkFvDaPYmVvHJ7f+3kbJ
IAdN/5O2kq61qoUBdR/LqlSkugzl0Hn8U+ETKzWzkLnNcLYl/A9k2vEBDs+WkSeV
/XQFyKYr21hfYxEA7ZZUT4DvcDVbFbEqdcIkADoH96TiMg1gwKYOHh+l2u1Cc9TC
XY6DS1hpZi9Iakl2hf+VQmNuW4QM9V0D711L8b17mI+4loH4fDW7bmdgKnm+tTYD
52T9NAd/v5Ym0IU5iOJyEoAtKtDuqQ==
=JxL5
-END PGP SIGNATURE-

Re: Scheduling 9.5

[Salvatore Bonaccorso]

Hi Cyril,

On Tue, May 15, 2018 at 10:49:46PM +0200, Cyril Brulebois wrote:
> Heya,
> 
> Jonathan Wiltshire  (2018-05-14):
> > We're due a point release any day now. Please indicate your
> > availablility out of:
> > 
> >  - May 26th (meaning freeze this coming weekend, which might be a big
> >ask)
> >  - Jun 2nd (which may require an unusual SRM)
> >  - Jun 9th (getting quite a way out of cadence, but maybe that can't
> >be helped)
> 
> I'm fine with any pick.
> 
> I don't think we have any pending ABI bump for linux (this time), and
> the stretch branch in debian-installer.git seems quiet, so binNMUing d-i
> might be sufficient. I might have missed pu requests for d-i components
> though, but hopefully debian-boot@ will correct me if I'm wrong on this.

Adding Kernel team list explicitly to the loop only for this later
part, dropping other recipients which might not be interested for this
reply specifically.

Currently we are cherry-picking secrutiy fixes in our
stretch-security branch. In parallel there is work on the stretch
branch to update to a newer 4.9.x stable release and to have it
included in the next point release. Now if the later turns out to be
the case earlier than any DSA, then there will actually likely be a
ABI bump for the kernel (the update will be at least up to 4.9.102 and
there are too many ABI changes as they would be possible to avoid).

Context: https://salsa.debian.org/kernel-team/linux/merge_requests/30

Regards,
Salvatore

Re: Scheduling 9.5

[Cyril Brulebois]

Hi Salvatore,

Salvatore Bonaccorso  (2018-06-05):
> On Tue, May 15, 2018 at 10:49:46PM +0200, Cyril Brulebois wrote:
> > I don't think we have any pending ABI bump for linux (this time), and
> > the stretch branch in debian-installer.git seems quiet, so binNMUing d-i
> > might be sufficient. I might have missed pu requests for d-i components
> > though, but hopefully debian-boot@ will correct me if I'm wrong on this.
> 
> Adding Kernel team list explicitly to the loop only for this later
> part, dropping other recipients which might not be interested for this
> reply specifically.
> 
> Currently we are cherry-picking secrutiy fixes in our
> stretch-security branch. In parallel there is work on the stretch
> branch to update to a newer 4.9.x stable release and to have it
> included in the next point release. Now if the later turns out to be
> the case earlier than any DSA, then there will actually likely be a
> ABI bump for the kernel (the update will be at least up to 4.9.102 and
> there are too many ABI changes as they would be possible to avoid).
> 
> Context: https://salsa.debian.org/kernel-team/linux/merge_requests/30

Many thanks for the heads-up. I'll be on the lookout for a possible
late ABI bump then. Feel free to poke me when that gets accepted into
p-u so that I can adjust our git branch and perform a few build and
runtime tests.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature