Hi,
On Wed, Jan 19, 2011 at 11:23:11AM +0100, Daniel Baumann wrote:
> On 01/19/2011 10:24 AM, Holger Levsen wrote:
> > I do understand you being annoyed (or unhappy or "whatever") about this...
> the meaning of 'coordinate on a release date' is to *find* a suitable
> date *in advance*, not declare one and expect others to adapt.
well, we mainly follow [0]. The goal of this release is also to improve the
documentation, as this was mainly copied from the Lenny point release notes.
So usually the release planning is with ftp-masters, because they're the most
important actors in the picture for the release itself. This is also what
happened in this case. The press team happened to be included due to personal
overlap with the FTP team.
There are various teams with whom this has to be coordinated in the end. That
also was one the points of the announcement to d-d-a. It's true that the
announcement actually says "core teams", but in fact that did mean ftp-masters
and maybe a few pings on IRC. To that extent -live was likely forgotten
in the process.[1]
We did say that we aim for late December. So we're two months late, and at
this point we expect sort of a smooth ride to the release.
> true, on the one hand, ignoring debian-live for that is pretty impolite,
> on the other hand, more importantly, it would be nice to know, once and
> for all, by an authoritative answer of the release-team if debian-live
> is not anymore part of the release and that this is the reason why we
> are ignored, or if the release-team just has imperfect workflows that
> constantly 'forgets' about debian-live. that way, we can either stop
> care ourselfs, or help improving their workflow.
So what's still missing for Debian live? I do see these bugs you / the
live team filed with RC severity:
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603554
update isolinux theme for squeeze (and related bugs #603552 and
#598101)
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603974
needs to reconfigure console-setup
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604783
needs to have entries for regular installer
There are still two and a half weeks left to tackle those issues if they're
really release critical for Debian live. You did postpone them after the
VAC and as it seems that you're the only person currently working on those,
it would be nice if you could spend some work on them.
If some issues of them are not critical to have in r0, but rather in r1,
feel free to submit patches afterwards. But please tag the bugs accordingly.
For #603554 I somewhat agree that a common theming would be nice in terms of
keeping a coherent design, however this could still be provided with r1.
Squeeze isn't dead post-release, so a few fixups for polishing are welcome.
#603974 was reopened, I guess because the fix was incomplete? There's no
update to the bug report since Dec 26, 2010, so I don't know what the status of
this is.
#604783 doesn't look too hard to fix.
Did I miss critical issues?
> also, i asked this more than once already, but never got any answer at all.
Do you have any public pointers for this? I don't think we ignore such
questions when asked on the list, but it's of course possible for us to lose
track of issues on the way, which aren't filed as bugs. I hope it's
understandable, given the amount of mails we receive. If you indeed did
repeated pings afterwards and we did not reply, I'd be stunned, though.
> > But let me focus on the productive side now: does this release date work for
> > debian-live?
> i'm supposed to stay for a couple of days abroad visiting a friend and
> will have to rescedule, not sure how much the fees are for that.
We're sorry if we cannot accomodate everyone in the process. If you need any
help during the process, I guess that could be arranged. Although I wonder if
-live could just be handled by -cd during release, anyway. Maybe a tad late
for that, though.
Kind regards
Philipp Kern
[0] http://wiki.debian.org/Teams/ReleaseTeam/ReleaseCheckList
[1] As a matter of fact, core teams like the wanna-build team also weren't
consulted if that works for them, as we'll have to take down all the
buildds and resetup them for another suite. But that's mainly a
"take them down and fix them during the week after".
Attachment:
signature.asc
Description: Digital signature