Bug#678705: RFS: e2defrag/0.80 ITP: #678598
On 25/06/12 14:34, Phillip Susi wrote:
> On 6/25/2012 4:25 AM, Dmitrijs Ledkovs wrote:
>> Your decision whether you upload into Debian experimental or unstable
>> should not be affected by other derivative distribution policies. You
>> can request syncing packages from experimental into Ubuntu, but the
>> package will still land in Ubuntu's new queue and require verification.
>> You can always provide backports/ppa/etc regardless of the package
>> status in the archive.
>>
>> Given above, unstable or experimental?
>
> I'm still not sure why one would want to use experimental instead of
> unstable. It seems like it's just one more hoop people have to jump
> through ( adding one more entry to sources.list ) to use the package.
> I'm not necessarily opposed to it, I just don't see the benefit.
>
> Correct me if I'm wrong, but isn't experimental for testing a one off
> hack you want a few specific people to try, but you know it would cause
> breakage for other users and so would not be appropriate for unstable?
>
> If that's the case, then I'd say unstable is the place to go.
>
Depends. Generally Experimental is what you make of it.
http://wiki.debian.org/DebianExperimental
Many new upstream releases of large packages are cured in experimental
first, because it introduces packages to the archive and allows using
bts to file and track bugs.
Many large libraries and softwares are packaged in experimental first,
e.g.: gnome, kde stacks, gcc toolchain, minor libraries SONAME bumps. To
ease testing against other packages (e.g. ftbfs in experimental with
libfoo+1) and ease testing the package by experienced developers and users.
Uploading to experimental, means that a package will not be a candidate
for automatic transition into a stable release. This can also be
achieved by opening a "sticky" RC bug. "Don't close, until maintainer is
happy for the package to transition".
When the archive is frozen, experimental is used to package all new
software, to allow unstable->testing uploads & transitions without going
through testing-proposed-updates.
To sum up, experimental is a tool for a maintainer to govern the
per-package release cycle on top of debian.
I can see how you want it in unstable, and I am fine to sponsor it there.
--
Regards,
Dmitrijs.
Reply to: