Re: mc problem - solved.
[ Redirected to debian.user at Paul Seelig's insistence ]
Paul Seelig <pseelig@goofy.zdv.uni-mainz.de> writes:
> > No. New upstream versions do not go into stable without *very*
> > good reason.
>
> Well, the current mc-3.5.17 is an *old* development version which
> has since long been superseded by some 31 following patchlevels
> including serious bug fixing and quite some very worthy new features
> culminating into the switch from "mc-3.5.48" to "mc-4.0".
And it's 31 patch levels of new and untested (in Debian) code. Not to
mention that if you were to release it it would be a new maintainer
and completely new and untested Debian packaging.
> The latter is an officially released version by the official
> upstream maintainers and i'm sincerely of the opinion that we
> shouldn't accept any obsolete devel versions of programs in stable.
It's Debian policy (afaik) that as little as possible should go into
stable after release, and *definitely* as little as possible, if any,
new upstream releases. (The only exception to this is major security
holes, which is why xfree 3.3 might/will be going into bo-updates)
--
James
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: