Dear release team, ftpmasters, press team, cd team, d-i team,
The Release Team believes that the state of bullseye is pretty good.
Yes, there are some blocking bugs [1] and d-i and shim still need some
love, but the state is much better than we remembered from the same time
in buster.
Last time in the buster release cycle, it took quite a while to pick a >release date once it was clear that buster could get released. As we
believe that shorter freeze period are better for the spirit of
contributors to Debian, we'd like to avoid such an unnecessary delay
again, and we'd want to pick a tentative release date. We call it
tentative, because it would be the date where we do the bullseye release >assuming that the identified issues are resolved by then and that we
don't find new blocking issues between now and two weeks before that
proposed date. So, the date would not be the set-in-stone release date,
but obviously it would become more solid as we get near it.
We propose to aim for a release date in May. Would either of the
following work for you and do you have any preference?
- May 1
- May 8
- May 15
- May 22
- May 29
Dear release team, ftpmasters, press team, cd team, d-i team,
The Release Team believes that the state of bullseye is pretty good.
Yes, there are some blocking bugs [1] and d-i and shim still need some
love, but the state is much better than we remembered from the same time
in buster.
Last time in the buster release cycle, it took quite a while to pick a release date once it was clear that buster could get released. As we
believe that shorter freeze period are better for the spirit of
contributors to Debian, we'd like to avoid such an unnecessary delay
again, and we'd want to pick a tentative release date. We call it
tentative, because it would be the date where we do the bullseye release assuming that the identified issues are resolved by then and that we
don't find new blocking issues between now and two weeks before that
proposed date. So, the date would not be the set-in-stone release date,
but obviously it would become more solid as we get near it.
We propose to aim for a release date in May. Would either of the
following work for you and do you have any preference?
- May 1
- May 8
- May 15
- May 22
- May 29
The Release Team believes that the state of bullseye is pretty good.
Yes, there are some blocking bugs [1] and d-i and shim still need some
love, but the state is much better than we remembered from the same
time in buster.
Last time in the buster release cycle, it took quite a while to pick a release date once it was clear that buster could get released. As we
believe that shorter freeze period are better for the spirit of
contributors to Debian, we'd like to avoid such an unnecessary delay
again, and we'd want to pick a tentative release date. We call it
tentative, because it would be the date where we do the bullseye
release assuming that the identified issues are resolved by then and
that we don't find new blocking issues between now and two weeks
before that proposed date. So, the date would not be the set-in-stone
release date, but obviously it would become more solid as we get near
it.
We propose to aim for a release date in May. Would either of the
following work for you and do you have any preference?
- May 1
- May 8
- May 15
- May 22
- May 29
Hi,
Paul Gevers <elbrus@debian.org> (2021-04-09):
The Release Team believes that the state of bullseye is pretty good.
Yes, there are some blocking bugs [1] and d-i and shim still need some love, but the state is much better than we remembered from the same
time in buster.
As already explained, trying to release in April/May wasn't quite anticipated, and there's still ground to cover on the d-i side.
Hi,
Cyril Brulebois <kibi@debian.org> wrote (Sat, 10 Apr 2021 11:54:59 +0200):
Hi,
Paul Gevers <elbrus@debian.org> (2021-04-09):
The Release Team believes that the state of bullseye is pretty good.
Yes, there are some blocking bugs [1] and d-i and shim still need some love, but the state is much better than we remembered from the same
time in buster.
As already explained, trying to release in April/May wasn't quite anticipated, and there's still ground to cover on the d-i side.
Trying to minimize the work load for kibi:
@kibi: (given there are no objections against this from you?):
Maybe the release-team could look into the pending unblock issues for d-i
in the meantime?
Most of them should be quite unproblematic, since they only contain translation
updates.
A bit more of an issue would be tasksel.
1. Currently there is 3.65 in sid, which needs to migrate to bullseye.
2. A problem came up during freeze regarding input methods for several
languages:
Starting with bullseye, GNOME depends on ibus, which is not fully
compatible with the view of some language teams, who would like to
prefer fcitx.
The best way to get this situation fixed would require some new
binary packages to be added to Bullseye (would only be tasks packages,
so no new code/functions to be added!).
A thread regarding this started at
https://lists.debian.org/debian-boot/2021/03/msg00058.html
and the release-team was also added to the loop at some point.
Maybe release-team could look into this too, and try to make a
decision?
Holger"When it's ready."
"When does the new Debian release come out?"
Dear release team, ftpmasters, press team, cd team, d-i team,
We propose to aim for a release date in May. Would either of the
following work for you and do you have any preference?
- May 1
- May 8
- May 15
- May 22
- May 29
Can you please let us know if/when you're available?
May 1 CD, Press
May 8 CD, Press
May 15 CD
May 22 CD, Press
May 29 (CD)
I've seen replies from Steve for CD, from Donald for Press and Cyril
for d-i. Can you please let us know if/when you're available?
May 1 CD, Press
May 8 CD, Press
May 15 CD
May 22 CD, Press
May 29 (CD)
[d-i: the later the better]
Seems like our current best option is May 22 if you can make it.
I've seen replies from Steve for CD, from Donald for Press and Cyril for
d-i. Can you please let us know if/when you're available?
May 1 CD, Press
May 8 CD, Press
May 15 CD
May 22 CD, Press
May 29 (CD)
[d-i: the later the better]
Seems like our current best option is May 22 if you can make it.
We propose to aim for a release date in May. Would either of the
following work for you and do you have any preference?
- May 1
- May 8
- May 15
- May 22
- May 29
I've seen replies from Steve for CD, from Donald for Press and Cyril
for d-i. Can you please let us know if/when you're available?
May 1 CD, Press
May 8 CD, Press
May 15 CD
May 22 CD, Press
May 29 (CD)
[d-i: the later the better]
Seems like our current best option is May 22 if you can make it.
Seems like our current best option is May 22 if you can make it.
That's definitely not what I would call “best option” from an
installer point of view.
D-I Bullseye RC 1 was published a few hours ago. And at the risk of
sounding like a broken record: I have *absolutely no guarantee* to
have a fix or workaround for the amdgpu issue in less than a month,
that would be tested somewhat.
Can we please *not* release with black screens for AMD users?
I hear you. So, I fear that we're getting into a situation where
everything except the installer is more or less ready for the bullseye release. (Well assuming the shim is signed any time soon).
D-I Bullseye RC 1 was published a few hours ago. And at the risk of sounding like a broken record: I have *absolutely no guarantee* to
have a fix or workaround for the amdgpu issue in less than a month,
that would be tested somewhat.
Can we please *not* release with black screens for AMD users?
Indeed, let's not. But can't we get the full Debian community on board
to search for good solution? I have the feeling there's much interest
to release sooner rather than late, so maybe there's brains we can use
to help the installer forward? I'm going to draft a bits shortly, is
there a bug number or mail thread we can point at?
Also, I recognize that the debian-installer is largely handled by you
alone. I estimate that it's not going to help you on the short term if
people volunteer to help with the coding as you would be spending time
on on-boarding them. So, how can we, the Debian Community, help you
getting the installer in releasable shape?
I can think of testing RC1, but what else? Do you have the right
hardware available for the amdgpu issue? Can people try out solutions
for you? Tell us, or tell us how to find out.
That said, I still think it's good to keep May 22 in the agenda as an
option to do the release, with the remark that we'll not release when
we're not ready (as Debian always does).
No, I don't have any amdgpu hardware at the moment; but yes, I have
leader@'s checklist handy for when I can allocate some time to plan for
this.
I'm trusting the release team to block until d-i is ready, from what I understand the date that they're trying to find in May is just a
tentative date. Would it also make sense to keep another tentative date
for June as a back-up? (I'm thinking that it might make it easier to
plan now than to scramble again in May, but if you feel different then
that's fine too).
D-I Bullseye RC 1 was published a few hours ago. And at the risk of
sounding like a broken record: I have *absolutely no guarantee* to
have a fix or workaround for the amdgpu issue in less than a month,
that would be tested somewhat.
Can we please *not* release with black screens for AMD users?
Indeed, from this and the last few posts in the discussion it reads that perhaps June is the better option for the 'timed' ready when ready
release date.
I think it would allow for extra care to be given in the areas needed
and would as Paul suggested allow the larger community to pull
together to help resolve some of the issues.
Hi all,
On 24-04-2021 00:41, Donald Norwood wrote:
Indeed, from this and the last few posts in the discussion it reads that perhaps June is the better option for the 'timed' ready when ready
release date.
The progress of fixing the blocking issues in the debian-installer is
good enough to start thinking again about a tentative bullseye release
date (see for more details in the quote below). Assuming all goes well
with RC2 and RC3, we'd be looking at the following candidate release dates:
26 June
3 July
10 July
17 July
24 July
Can you let us know which date work for you and which don't?
I think it would allow for extra care to be given in the areas needed
and would as Paul suggested allow the larger community to pull
together to help resolve some of the issues.
The installer team needs everybody's help to test the d-i release
candidates, to see if the issues that are being solved now are handled correctly across as many different machines as possible. If anybody has better ideas than the wiki page that kibi suggested in his e-mail below,
then let us know. Otherwise I'll probably see if I can set up something
like that shortly.
Paul
On 24-04-2021 00:41, Donald Norwood wrote:
Indeed, from this and the last few posts in the discussion it reads that
perhaps June is the better option for the 'timed' ready when ready
release date.
The progress of fixing the blocking issues in the debian-installer is
good enough to start thinking again about a tentative bullseye release
date (see for more details in the quote below). Assuming all goes well
with RC2 and RC3, we'd be looking at the following candidate release dates:
26 June
3 July
10 July
17 July
24 July
Can you let us know which date work for you and which don't?
I think it would allow for extra care to be given in the areas needed
and would as Paul suggested allow the larger community to pull
together to help resolve some of the issues.
The installer team needs everybody's help to test the d-i release
candidates, to see if the issues that are being solved now are handled >correctly across as many different machines as possible. If anybody has >better ideas than the wiki page that kibi suggested in his e-mail below,
then let us know. Otherwise I'll probably see if I can set up something
like that shortly.
Paul
On 5/29/21 9:12 AM, Steve McIntyre wrote:
On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
Assuming all goes well
with RC2 and RC3, we'd be looking at the following candidate release dates: >>>
26 June
3 July
10 July
17 July
24 July
Can you let us know which date work for you and which don't?
I can do the
17th and 24th of July just fine.
Press can do both the 17th and the 24th. Perhaps we add an additional 3 dates?
Hi,
On 30-05-2021 06:35, Donald Norwood wrote:
On 5/29/21 9:12 AM, Steve McIntyre wrote:
On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
Assuming all goes well
with RC2 and RC3, we'd be looking at the following candidate release dates:
26 June
3 July
10 July
17 July
24 July
Can you let us know which date work for you and which don't?
[Steve]
I can do the
17th and 24th of July just fine.
Asking a question I think most people know the answer to, but CD without Steve is no option? Don't get me wrong, I don't want to push otherwise,
but I just want to understand the options. So much in Debian is based on "rituals", it's not always clear what's needed and what is just (nearly) always done in a certain way.
[Press]
Press can do both the 17th and the 24th. Perhaps we add an additional 3 dates?
Yes, let's do that, so the list becomes:
26 June
3 July
10 July
17 July [Steve (CD), press]
24 July [Steve (CD), press]
31 July
7 August
14 August
Paul
On 30-05-2021 06:35, Donald Norwood wrote:
On 5/29/21 9:12 AM, Steve McIntyre wrote:
On Fri, May 28, 2021 at 10:17:55PM +0200, Paul Gevers wrote:
Assuming all goes well
with RC2 and RC3, we'd be looking at the following candidate release dates:
26 June
3 July
10 July
17 July
24 July
Can you let us know which date work for you and which don't?
[Steve]
I can do the
17th and 24th of July just fine.
Asking a question I think most people know the answer to, but CD without >Steve is no option? Don't get me wrong, I don't want to push otherwise,
but I just want to understand the options. So much in Debian is based on >"rituals", it's not always clear what's needed and what is just (nearly) >always done in a certain way.
[Press]
Press can do both the 17th and the 24th. Perhaps we add an additional 3
dates?
Yes, let's do that, so the list becomes:
26 June
3 July
10 July
17 July [Steve (CD), press]
24 July [Steve (CD), press]
31 July [Steve (CD)]
7 August [Steve (CD)]
14 August [Steve (CD)]
26 June
3 July
10 July
17 July [Steve (CD), press]
24 July [Steve (CD), press]
31 July
7 August
14 August
[Press]
Press can do both the 17th and the 24th. Perhaps we add an additional 3 dates?
Yes, let's do that, so the list becomes:
26 June
3 July
10 July
17 July [Steve (CD), press]
24 July [Steve (CD), press]
31 July
7 August
14 August
26 June
3 July
10 July
17 July [Steve (CD), press]
24 July [Steve (CD), press]
31 July
7 August
14 August
We've been slowly working up to getting other people able to do image releases, but I don't think we're *quite* there yet. Maybe on the next
point release Andy could do it all without me watching and helping,
but we want to work that out and I'm not sure a new major release is
the right time to try this!
26 June
3 July
10 July
17 July [Steve (CD), press]
24 July [Steve (CD), press]
31 July
7 August
14 August
26 June [Ansgar (ftp)]
3 July [Ansgar (ftp), Sebastian (release), Paul (release)]
10 July [Steve (CD) MAYBE , Ansgar (ftp), Paul (release)]
17 July [Steve (CD), press, Ansgar (ftp), Paul (release)]
24 July [Steve (CD), press, Ansgar (ftp), Sebastian (release)]
31 July [Steve (CD), press, Ansgar (ftp), Sebastian (release)]
7 August [Steve (CD), press, Ansgar (ftp), Sebastian (release)]
14 August [Steve (CD), press, Ansgar (ftp), Sebastian (release)]
With the availability of Adam now known (and some off-list info), we have:
26 June
[Ansgar (ftp), Sebastian (release), Adam (release)]
3 July
[Ansgar (ftp), Paul (release), Adam (release)]
10 July
[Steve (CD) MAYBE , Ansgar (ftp), Paul (release), Adam (release),
Graham (release)]
17 July
[Steve (CD), press, Ansgar (ftp), Paul (release)]
24 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release),
Graham (release)]
31 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
7 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
14 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
So, what to pick? We still believe that shorter freezes are better for
the Debian community as a whole, so Steve can you look at turning your
maybe on 10 July into a "lets go for this"? If the answer is no, than
lets pick 24 July as the *tentative* release date.
Regardless of which of the two we pick, I propose we decide two weeks
before if it's going to be final.
And, relevant for every maintainer of non-key packages without passing autopkgtests, the full freeze will start two weeks before the
*tentative* release. The means that, with traditionally the last week
being totally frozen, the last week that packages can migrate *all*
packages need manual unblocks by the release team.
Hi all,
On 06-06-2021 20:03, Paul Gevers wrote:
With the availability of Adam now known (and some off-list info),
we have:
So, what to pick? We still believe that shorter freezes are better
for
the Debian community as a whole, so Steve can you look at turning
your
maybe on 10 July into a "lets go for this"? If the answer is no,
than
lets pick 24 July as the *tentative* release date.
Nevermind 10 July. Steve, you can stop contemplating about it. We'll
go for 24 July as the *tentative* release date.
Hi all,
On 06-06-2021 20:03, Paul Gevers wrote:
With the availability of Adam now known (and some off-list info), we have: >>
26 June
[Ansgar (ftp), Sebastian (release), Adam (release)]
3 July
[Ansgar (ftp), Paul (release), Adam (release)]
10 July
[Steve (CD) MAYBE , Ansgar (ftp), Paul (release), Adam (release),
Graham (release)]
17 July
[Steve (CD), press, Ansgar (ftp), Paul (release)]
24 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release),
Graham (release)]
31 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
7 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
14 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
So, what to pick? We still believe that shorter freezes are better for
the Debian community as a whole, so Steve can you look at turning your
maybe on 10 July into a "lets go for this"? If the answer is no, than
lets pick 24 July as the *tentative* release date.
Nevermind 10 July. Steve, you can stop contemplating about it. We'll go
for 24 July as the *tentative* release date.
Regardless of which of the two we pick, I propose we decide two weeks
before if it's going to be final.
So, we'll decide around 10 July.
And, relevant for every maintainer of non-key packages without passing
autopkgtests, the full freeze will start two weeks before the
*tentative* release. The means that, with traditionally the last week
being totally frozen, the last week that packages can migrate *all*
packages need manual unblocks by the release team.
And the Full Freeze will start on 10 July too.
Paul
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:
Hi all,[...]
On 06-06-2021 20:03, Paul Gevers wrote:
With the availability of Adam now known (and some off-list info),
we have:
Unfortunately I've just discovered that I was given the wrong date forSo, what to pick? We still believe that shorter freezes are betterNevermind 10 July. Steve, you can stop contemplating about it. We'll
for
the Debian community as a whole, so Steve can you look at turning
your
maybe on 10 July into a "lets go for this"? If the answer is no,
than
lets pick 24 July as the *tentative* release date.
go for 24 July as the *tentative* release date.
a family event, so I'm actually going to be AFK for most of the 24th.
:-(
Apologies for sticking a slight spanner in the works at this stage.
Adam
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:
Nevermind 10 July. Steve, you can stop contemplating about it. We'll
go for 24 July as the *tentative* release date.
Unfortunately I've just discovered that I was given the wrong date for
a family event, so I'm actually going to be AFK for most of the 24th.
:-(
Apologies for sticking a slight spanner in the works at this stage.
So, if I did all the booking right (including updates from IRC) we now have:
26 June
[Ansgar (ftp), Sebastian (release), Adam (release)]
3 July
[Ansgar (ftp), Paul (release), Adam (release)]
10 July
[Steve + Andy (CD), Paul (release), Adam (release), Graham (release)]
17 July
[Steve (CD), press, Ansgar (ftp), Paul (release)]
24 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release),
Graham (release)]
31 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
7 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
14 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
The first available date is 31 July, so let's shift all my dates another >week.
17 July: Hard Freeze & confirmation of the release date
31 July: ** tentative ** release date
Hi all again,
On 07-06-2021 23:08, Adam D. Barratt wrote:
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote:Those things happen. It's the price we pay for our bus factors (which we should fix/are fixing).
Nevermind 10 July. Steve, you can stop contemplating about it. We'llUnfortunately I've just discovered that I was given the wrong date for
go for 24 July as the *tentative* release date.
a family event, so I'm actually going to be AFK for most of the 24th.
:-(
Apologies for sticking a slight spanner in the works at this stage.
So, if I did all the booking right (including updates from IRC) we now have:
26 June
[Ansgar (ftp), Sebastian (release), Adam (release)]
3 July
[Ansgar (ftp), Paul (release), Adam (release)]
10 July
[Steve + Andy (CD), Paul (release), Adam (release), Graham (release)]
17 July
[Steve (CD), press, Ansgar (ftp), Paul (release)]
24 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release),
Graham (release)]
31 July
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
7 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
14 August
[Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)]
The first available date is 31 July, so let's shift all my dates another week.
17 July: Hard Freeze & confirmation of the release date
31 July: ** tentative ** release date
Paul
On Tue, Jun 08, 2021 at 08:50:55PM +0200, Paul Gevers wrote:
31 July: ** tentative ** release date
Cool, works for me. Pencilled into my calendar now. :-)
With less than three weeks to go until the tentative release date, I
would love to confirm the date by now, but there is a serious issue with crucial infrastructure (cdbuilder.d.o). Apart from this issue (and what
it means for solving the debian-installer blocking issues in time), I'm
not aware of other blocking issues, so let's hope the teams involved can recover in time.
Hi all,
On 11-07-2021 21:11, Paul Gevers wrote:
With less than three weeks to go until the tentative release date, I
would love to confirm the date by now, but there is a serious issue with
crucial infrastructure (cdbuilder.d.o). Apart from this issue (and what
it means for solving the debian-installer blocking issues in time), I'm
not aware of other blocking issues, so let's hope the teams involved can
recover in time.
Albeit there is some progress, we think it better for the people
involved to now say that we will *not* release on July 31.
Unfortunately, that means that we have to start looking for a new date
again. Assuming what we'll learn in the upcoming week or two is good, I >propose to already start the list below with two weeks after the
previous date. Upcoming time is around DebConf, I can imagine it could
even be an advantage, especially as that's on-line, let's see.
14 August (day before DebCamp)
21 August (last day of DebCamp)
RT: elbrus
28 August (DebConf)
RT: elbrus
4 September
RT: elbrus
11 September:
RT: elbrus
On Sat, Jul 17, 2021 at 10:25:17PM +0200, Paul Gevers wrote:Doable.
Hi all,
On 11-07-2021 21:11, Paul Gevers wrote:
With less than three weeks to go until the tentative release date, I
would love to confirm the date by now, but there is a serious issue with >>> crucial infrastructure (cdbuilder.d.o). Apart from this issue (and what
it means for solving the debian-installer blocking issues in time), I'm
not aware of other blocking issues, so let's hope the teams involved can >>> recover in time.
Albeit there is some progress, we think it better for the people
involved to now say that we will *not* release on July 31.
Unfortunately, that means that we have to start looking for a new date
again. Assuming what we'll learn in the upcoming week or two is good, I
propose to already start the list below with two weeks after the
previous date. Upcoming time is around DebConf, I can imagine it could
even be an advantage, especially as that's on-line, let's see.
14 August (day before DebCamp)
Works for me for images teamHalf of the press team is available this day so it is not ideal.
21 August (last day of DebCamp)
RT: elbrus
Awkward - wife has plans for us that evening.
Labor day weekend in the U.S. Not a good weekend.28 August (DebConf)
RT: elbrus
Debian UK BBQ, argh
4 September
RT: elbrus
Works fine for meHappy Anniversary!
11 September:
RT: elbrus
That's the week of my wedding anniversary, I'll be on VAC.
Hi!Works for me
On 7/17/21 4:58 PM, Steve McIntyre wrote:
On Sat, Jul 17, 2021 at 10:25:17PM +0200, Paul Gevers wrote:Doable.
Hi all,
On 11-07-2021 21:11, Paul Gevers wrote:
With less than three weeks to go until the tentative release date, IAlbeit there is some progress, we think it better for the people
would love to confirm the date by now, but there is a serious issue with >>>> crucial infrastructure (cdbuilder.d.o). Apart from this issue (and what >>>> it means for solving the debian-installer blocking issues in time), I'm >>>> not aware of other blocking issues, so let's hope the teams involved can >>>> recover in time.
involved to now say that we will *not* release on July 31.
Unfortunately, that means that we have to start looking for a new date
again. Assuming what we'll learn in the upcoming week or two is good, I
propose to already start the list below with two weeks after the
previous date. Upcoming time is around DebConf, I can imagine it could
even be an advantage, especially as that's on-line, let's see.
14 August (day before DebCamp)
Sorry - awayWorks for me for images teamHalf of the press team is available this day so it is not ideal.
21 August (last day of DebCamp)Awkward - wife has plans for us that evening.
RT: elbrus
away at ^^28 August (DebConf)Debian UK BBQ, argh
RT: elbrus
doable - Isy and I will be unavailable before 1300hrs UTCLabor day weekend in the U.S. Not a good weekend.
4 September
RT: elbrus
Works fine for me
Works for meHappy Anniversary!11 September:That's the week of my wedding anniversary, I'll be on VAC.
RT: elbrus
Could we put forth September 18th? We are good for that day without any issues.Works for me
14 August (day before DebCamp)
21 August (last day of DebCamp)
RT: elbrus
28 August (DebConf)
RT: elbrus
4 September
RT: elbrus
11 September:
RT: elbrus
Albeit there is some progress, we think it better for the people
involved to now say that we will *not* release on July 31.
Unfortunately, that means that we have to start looking for a new date
again. Assuming what we'll learn in the upcoming week or two is good,
I
propose to already start the list below with two weeks after the
previous date. Upcoming time is around DebConf, I can imagine it could
even be an advantage, especially as that's on-line, let's see.
14 August (day before DebCamp)
21 August (last day of DebCamp)
RT: elbrus
28 August (DebConf)
RT: elbrus
4 September
RT: elbrus
11 September:
RT: elbrus
Hi all,
On 11-07-2021 21:11, Paul Gevers wrote:
With less than three weeks to go until the tentative release date, I
would love to confirm the date by now, but there is a serious issue with crucial infrastructure (cdbuilder.d.o). Apart from this issue (and what
it means for solving the debian-installer blocking issues in time), I'm
not aware of other blocking issues, so let's hope the teams involved can recover in time.
Albeit there is some progress, we think it better for the people
involved to now say that we will *not* release on July 31.
Unfortunately, that means that we have to start looking for a new date
again. Assuming what we'll learn in the upcoming week or two is good, I propose to already start the list below with two weeks after the
previous date. Upcoming time is around DebConf, I can imagine it could
even be an advantage, especially as that's on-line, let's see.
14 August (day before DebCamp)
21 August (last day of DebCamp)
RT: elbrus
28 August (DebConf)
RT: elbrus
4 September
RT: elbrus
11 September:
RT: elbrus
We currently don't have any day yet with all involved
teams comfortably present, the one coming closest is 4 September.
Somebody from ftp available on 14 august?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 113 |
| Nodes: | 8 (1 / 7) |
| Uptime: | 43:16:50 |
| Calls: | 2,499 |
| Calls today: | 1 |
| Files: | 8,651 |
| Messages: | 1,908,299 |