Re: Uploads to experimental instead of unstable (was RFS: vbetool (QA upload))
Hello Neil,
On Thu, Dec 11, 2008 at 11:08, Neil Williams <codehelp@debian.org> wrote:
> Unstable is also "closed" so that other packages can migrate more
> easily. Uploads not related to Lenny should go into experimental. New
can you point to ufficial documentation stating this? (ok, it's a
joke, I know there's none) While it's a wise suggestions, it's not a
law and it's not strictly to be followed. The way you expressed it
seems like "do not ever upload to unstable while we are in freeze"
which is, of course, not true.
> upstream versions have a lower likelihood of being deemed acceptable
> for migration by the release team. However, you also need to fix
> something in the upload that is relevant to the release in order for
> the release team to allow the migration. A "ping" is a waste of time -
> a fix for an RC bug is what is needed. If there is no RC bug to fix
And even inportant bug are welcome to be fixed for a lenny-targetted
upload, while basing the decision only on bugs priority could be
misleading.
> with this upload then upload to experimental, not unstable (or don't
> upload until after Lenny is released).
so are you saying that it was time wasted? I don't think so, and I
think this upload can go into unstable without problems.
> It's a bit more complicated than that - 'testing-proposed-updates' is
> for times when unstable already has a newer version of the package that
> will not migrate and an RC bug is found in the older version in
> testing. The preferred method to fix RC bugs is to be able to upload to
> unstable and migrate with permission from the release team. Uploading
> other cruft to unstable gets in the way of that process.
Cruft? so doing a QA upload trying to get the package in a good shape
is "cruft" for you? nice judgment :)
Of course, while we are trying to "stabilize" the distribution in
testing, we should try to fix RC bugs opened (avoiding to introduce
new, ok) but that doesn't mean we have to stop all other activities
waiting for lenny to be released. Consider the situation where a guy
want help but doesn't have the skill to fix the opened RC bugs: is he
not "allowed" to package new tools, do qa uploads or update his own
pkgs?
> If a package on mentors is *not* meant to be part of Lenny, if your
> upload does not fix an RC bug in Lenny, then consider unstable
> off-limits and make your upload into experimental - or don't upload at
> all and work on an RC bug instead.
see above.
> The more differences there are between unstable and testing at this
> time, the harder it can be to actually fix the bugs which then means
> that the entire freeze goes on for longer. Ignoring this problem
> doesn't make it go away - uploading random junk to unstable actually
> prolongs the problem for everyone else. Stop it, please.
Please stop be so rude to newcomer maintainers. It won't help you nor
the guy willing to help: after such a reply I'll think twice the next
time I want to help Debian. and we do not want this!
Cheers,
Sandro
PS: I removed some parts of the original post since already expressed
in other terms in quoted text.
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Reply to: