Re: Bug#835533: dasher: Please package Dasher 5.0 beta
On October 6, 2016 8:51:59 AM EDT, Adrian Bunk <email@example.com> wrote:
>On Thu, Oct 06, 2016 at 02:46:44AM -0400, Scott Kitterman wrote:
>> As frustrating as occasional removal/reintroduction cycles are, they
>are rare enough that despite the frustration when they occur it's
>really not worth the effort it would take to avoid them completely.
>This assumes that all users are developers who are following unstable.
>The vast majority of Debian users won't use stretch until after it
>And even if a user does use unstable or testing, there is no clear way
>for a non-developer do get a removed package back into unstable.
>It is a problem for users when Debian is a revolving door
>for packages that get ITP'ed into one stable and then disappear
>without a good reason for removal in a later stable.
>Example maintainer opinion: [1,2]
> If we orphan 2.x someone might fix the RC bug and get it back into
> At this point I think releasing stretch with 2.x would be worse than
> releasing stretch without freeradius.
>When a user who uses FreeRADIUS 2.2.5 in jessie upgrades to stretch
>after it became stable, is it worse for the user he gets FreeRADIUS
>in stretch with 3 years (or 5 years with LTS) of security support,
>or if he gets no FreeRADIUS in stretch?
>FreeRADIUS is high-profile enough that many Debian developers do care
>and new maintainers were quickly found. Many other packages are not.
This is all true, but in the end, Debian is a do-acracy. While we should try to do the best for our users, there's no way we can do everything for everyone. Users who want to increase the chances our next release scratches whatever their personal itch is need to get involved with development.