Question for all candidates: Release process
This is for all candidates.
Releasing is regularly the hardest thing that Debian does, not just
technically but also socially. Apart from the standard issues of setting
deadlines, RC bug counts being high, and similar difficult technical
issues, the process seems to eat volunteers. There's usually always at
least some frustration, anger, and upsetness, and there seems to usually
be at least one resignation over the course of a release, often in a way
that hurts other activities in Debian for a time.
Do you have any ideas how, as DPL, you would (or even could) address this?
I'm personally the most concerned with the social issues. A delayed
release can be frustrating but doesn't have that much negative impact, but
volunteers with enough knowledge of Debian to be able to serve as release
managers or helpers are rare. And usually the arguments not only hurt
their contributions to Debian but usually hurt the contributions to Debian
of the people on the other side of the argument as well, who are often
also valuable and difficult-to-replace volunteers.
Do you have any thoughts about how to resolve release issues with less
hurt and negative impact to the project all around?
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>