[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#684044: unblock: nodejs/0.6.19~dfsg1-4



Raphael Hertzog <hertzog@debian.org> (20/08/2012):
> Of course to avoid being overwhelmed with new packages (which could
> create supplementary workloads later in the freeze), you should not
> allow them by default. But when a maintainer does the effort to argue
> for its inclusion, he's likely also going to do the effort of keep it
> in a state where it's releasable (and if not, you can always use the
> large stick "ok, but if anything goes wrong, we'll remove it again
> since you're going in too late").

I can't imagine people uploading, whining because they didn't make it in
time (a 1-year announce surely isn't enough), and running away after
that. Oh wait.

> Coming back to this specificic case, we have lots of users of node and
> some popular node-based tools (I'm using node-less myself) so I feel
> that it's quite unproductive to keep those tools out of the release
> when a part of the delay has been due to the tech-ctte...

Blaming that on tech-ctte, seriously? #597571 is from *** 2010 ***.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: