Dear all,
On 15-03-2023 21:33, Jonathan Wiltshire wrote:
We're overdue for 11.7 and need it done with a keyring update included before bookworm can be released. The wheels are turning on the keyring so how do dates in April look for everybody? Saturdays are 1st (probably too soon), 8th, 15th, 22nd and 29th.
I know some people will call me crazy, but can and should we combine
this with finding a release date for bookworm?
From where I'm looking, bookworm is looking pretty good. Obviously
we'll have to follow through on the flurry of unblock requests that came
in after the hard freeze, but that should be manageable in a couple of
weeks. kibi just told me on IRC that asking this question now is not
crazy from a d-i point of view. That hopefully means that around the end
of April, also the bookworm d-i should™ be ready for release (kibi, I'm sure you'll comment on this if I got you wrong or if you want to provide
more details).
So, shall we add availability for May too? 6th, 13th, 20th (Ascension weekend), and 27th (coincides with DebianReunionHamburg)?
Paul
From where I'm looking, bookworm is looking pretty good. Obviously
we'll have to follow through on the flurry of unblock requests that
came in after the hard freeze, but that should be manageable in a
couple of weeks. kibi just told me on IRC that asking this question
now is not crazy from a d-i point of view.
That hopefully means that around the end of April, also the bookworm
d-i should™ be ready for release (kibi, I'm sure you'll comment on
this if I got you wrong or if you want to provide more details).
So, shall we add availability for May too? 6th, 13th, 20th (Ascension weekend), and 27th (coincides with DebianReunionHamburg)?
From where I'm looking, bookworm is looking pretty good. Obviously we'll have >to follow through on the flurry of unblock requests that came in after the >hard freeze, but that should be manageable in a couple of weeks. kibi just >told me on IRC that asking this question now is not crazy from a d-i point of >view. That hopefully means that around the end of April, also the bookworm >d-i should™ be ready for release (kibi, I'm sure you'll comment on this if I >got you wrong or if you want to provide more details).
So, shall we add availability for May too? 6th, 13th, 20th (Ascension >weekend), and 27th (coincides with DebianReunionHamburg)?
Hi,
With the point release scheduled for April 29th, it's probably good to have >at least one weekend in between, or do people not mind doing two weekends in >a row?
On 17-03-2023 15:59, Steve McIntyre wrote:
On Thu, Mar 16, 2023 at 11:26:00AM +0100, Paul Gevers wrote:
So, shall we add availability for May too? 6th, 13th, 20th (Ascension
weekend), and 27th (coincides with DebianReunionHamburg)?
I could do the 6th and 13th, but I'm away on vacation 20th and 27th
(and 3rd June).
If I did the bookkeeping correctly, the missing necessary teams are press and >release team, as I now have:
kibi - 6, 13, 20, 27 d-i
mhy - 6, 13, 20, 27 ftp
Sledge - 6, 13 CD
Luna - 6, 20 CD testing
I can help 6 (probably), 13 and 27, but I don't have the signing key and I >haven't witnessed all details from our side so I'm not comfortable doing it >alone even if I could get my hands on the key.
elbrus - 13, 27 release team
Hi,
With the point release scheduled for April 29th, it's probably good to
have at least one weekend in between, or do people not mind doing two weekends in a row?
On 17-03-2023 15:59, Steve McIntyre wrote:
On Thu, Mar 16, 2023 at 11:26:00AM +0100, Paul Gevers wrote:
So, shall we add availability for May too? 6th, 13th, 20th (Ascension
weekend), and 27th (coincides with DebianReunionHamburg)?
I could do the 6th and 13th, but I'm away on vacation 20th and 27th
(and 3rd June).
If I did the bookkeeping correctly, the missing necessary teams are
press and release team, as I now have:
kibi - 6, 13, 20, 27 d-i
mhy - 6, 13, 20, 27 ftp
Sledge - 6, 13 CD
Luna - 6, 20 CD testing
I can help 6 (probably), 13 and 27, but I don't have the signing key and
I haven't witnessed all details from our side so I'm not comfortable
doing it alone even if I could get my hands on the key.
elbrus - 13, 27 release team
Paul
The 13th is in a month from today. We're still missing press and acooked solution for the release team.
I'll be at the Debian Reunion Hamburg on the 27, so that feels like agood day (albeit probably missing talks) to do the release if I were to
Dear all,
Progress \o/.
On 13-04-2023 11:29, Paul Gevers wrote:
For me to do the release, I'd need to get my hands on the key.
I'm in contact with Jonathan and we're convinced we'll be able to
get the key to me in time.
On Thu, 2023-04-20 at 11:32 +0200, Paul Gevers wrote:
Dear all,
Progress \o/.
On 13-04-2023 11:29, Paul Gevers wrote:
For me to do the release, I'd need to get my hands on the key.
I'm in contact with Jonathan and we're convinced we'll be able to
get the key to me in time.
I'm aware this still needs much more input from me :-/ but as a quick
note, for the record it's key*s*. The Release files contain both
codenames and suite designations, so the moves of stable to oldstable
and oldstable to oldoldstable mean that buster and bullseye's Release
files will also need re-signing.
Regards,
Adam
Dear all,
Progress \o/.
On 13-04-2023 11:29, Paul Gevers wrote:
For me to do the release, I'd need to get my hands on the key.
I'm in contact with Jonathan and we're convinced we'll be able to get the key >to me in time.
Which leaves finding a date (and me learning what to do :) ).
We have (if earlier mentioned dates still work for those involved):
May | June
kibi - 13, 20, 27 d-i
mhy - 13, 20, 27 ftp
Sledge - 13 CD
Luna - 20 CD testing
elbrus - 13 27, (3), 10, 24 release team
It seems a tiny bit late for 13 already, but still, would be awesome. What do >we think?
If we have somebody from CD to do 27 (yes, I remember Sledge can't
do that one), that would be great as it would be my preference; I'll have >lots of Debian people physically around me. As the DPL mentioned, we might >not want to block on press availability, although it would be real great if >we had them.
On Thu, Apr 20, 2023 at 11:32:49AM +0200, Paul Gevers wrote:
We have (if earlier mentioned dates still work for those involved):
May | June
kibi - 13, 20, 27 d-i
mhy - 13, 20, 27 ftp
Sledge - 13 CD
Luna - 20 CD testing
elbrus - 13 27, (3), 10, 24 release team
It seems a tiny bit late for 13 already, but still, would be
awesome. What do we think?
If we have somebody from CD to do 27 (yes, I remember Sledge can't
do that one), that would be great as it would be my preference; I'll
have lots of Debian people physically around me. As the DPL
mentioned, we might not want to block on press availability,
although it would be real great if we had them.
Unfortunately, the other person on the images team who has the
knowledge to do a release (Andy) is also away - we're on the same
vacation! May 27 and June 3 are both out for that reason.
On 13-04-2023 11:29, Paul Gevers wrote:
For me to do the release, I'd need to get my hands on the key.
I'm in contact with Jonathan and we're convinced we'll be able to
get the key to me in time.
Which leaves finding a date (and me learning what to do :) ).
We have (if earlier mentioned dates still work for those involved):
May | June
kibi - 13, 20, 27 d-i
mhy - 13, 20, 27 ftp
Sledge - 13 CD
Luna - 20 CD testing
elbrus - 13 27, (3), 10, 24 release team
It seems a tiny bit late for 13 already, but still, would be
awesome.
Hi all,
TL;DR: ftp & press input for June needed.
On 20-04-2023 18:29, Adam D. Barratt wrote:
The 13th does seem a bit close now, without having announced.
After some consideration today, and the vibe felt in this discussion, let's >not rush this, so let's skip May 13 (also giving Press some time, see below).
One other thing of note is that, unless I've missed some mail, there's
no press / publicity team member confirmed as available, which is
really a requirement.
Jonathan (DPL) mentioned earlier:
"""
Press team is in some slight limbo at the moment, I hope to help fix that >after the DPL election is over, in the mean time, it might be a good idea not >to block on them.
"""
If press is "really a requirement", we'll have to wait until this is settled.
From the CD side we know that with May 13 out, the rest of May is also out. >So we're looking for a date in June. For June, starting with 10, we have: >kibi - 10, 17, 24 d-i
Luna - 10, 17, 24 CD testing
elbrus - 10, 24 release team
adsb - 10, 17, 24 release team
On Thu, Apr 20, 2023 at 08:20:51PM +0200, Paul Gevers wrote:
Hi all,Sledge - 10, 17, 24 images team
TL;DR: ftp & press input for June needed.
On 20-04-2023 18:29, Adam D. Barratt wrote:
The 13th does seem a bit close now, without having announced.After some consideration today, and the vibe felt in this discussion, let's >> not rush this, so let's skip May 13 (also giving Press some time, see below).
One other thing of note is that, unless I've missed some mail, there'sJonathan (DPL) mentioned earlier:
no press / publicity team member confirmed as available, which is
really a requirement.
"""
Press team is in some slight limbo at the moment, I hope to help fix that
after the DPL election is over, in the mean time, it might be a good idea not
to block on them.
"""
If press is "really a requirement", we'll have to wait until this is settled.
From the CD side we know that with May 13 out, the rest of May is also out.
So we're looking for a date in June. For June, starting with 10, we have:
kibi - 10, 17, 24 d-i
Luna - 10, 17, 24 CD testing
elbrus - 10, 24 release team
adsb - 10, 17, 24 release team
Hi all,
Let's book June 10 as the bookworm release date. A more formal announcement >will follow.
On Sun, Apr 23, 2023 at 09:13:40PM +0200, Paul Gevers wrote:
Hi all,
Let's book June 10 as the bookworm release date. A more formal
announcement
will follow.
\o/
--
Steve McIntyre, Cambridge, UK.
steve@einval.com
Getting a SCSI chain working is perfectly simple if you remember that
there
must be exactly three terminations: one on one end of the cable, one on
the
far end, and the goat, terminated over the SCSI chain with a
silver-handled
knife whilst burning *black* candles. --- Anthony DeBoer
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 300 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 38:40:38 |
| Calls: | 6,708 |
| Calls today: | 1 |
| Files: | 12,241 |
| Messages: | 5,353,575 |