On Sun, Mar 10, 2013 at 03:52:23PM +0100, Magnus Holmgren wrote:
C. Not shipping pike7.8 in Wheezy.
I'm very much in doubt what the best course of action for Wheezy is, but I'm a bit tempted to recommend C based on the information I have.
Agreed, removal hint added.
So, unfortunately the release team removed Pike entirely from the next stable release of Debian, because I said that some of the bugs fixed by 7.8.700 were "rather serious". Can you help me elaborate on that? (pike-jira.lysator.liu.se seems rather down at the moment.) Certainly 7.8.352 is better than nothing at all?
well, if there are not enough debian users, what does it matter to them? sure it matters to us because we want pike easely available, but that's hardly an argument.
can you try referencing the release-notes on the nature of the bugs? which serious bugs have been fixed?
btw: for anyone interested i located the message quoted above: http://lists.debian.org/debian-release/2013/03/msg00277.html
the question here is: what information would they need in order to choose a or b?
if there are only few users is the risk of regressions more serious than not shipping pike at all? which will hurt users more? wouldn't dropping pike be the worst of all choices? i'd certainly call it a regression to pre-squeeze days.
unfortunately myself i am not really using debian anymore so i can't argue from an active user perspective.
would it help to have a maintainer team to prevent this from happening again?
i have been thinking about the idea of forming a team that includes all distributions, and as a team we'd maintain packages for debian, foresight, gentoo, osx and possibly also fedora, arch and others. i think most packaging problems are similar across distributions, so being one team we could help and support each other.
greetings, martin.