> Just so the motivation is clear: we are working on getting ready to
> shut down the old server. That means for each issue there we need to
> do one of the following:
Yes, I realize what you're doing.
> 1. fix it
> 2. move it
> 3. drop it
>
> If something is fairly minor and has not been touched in a long time
> then it means there isn't much community support for it. In this
> circumstance I'd say it's better to drop it than keep it, and if
> someone really does want it the worst case is that they have to
> create a new one on the new server (and hopefully with more details
> or a patch or such).
I see the point, however... were it me, I think I'd try and keep some
of those around. Even if they're minor, they're still things that
someone took the time to log in and say something about.
Perhaps there's a way to do something like this: mark some issues as
minor, such as this one, and just cut'n'paste them into a text file in
subversion, or something like that that means that they aren't lost
forever.
The world won't end either way, though, just thought I'd say something
in favor of keeping things around even if they're not being worked on.
--
David N. Welton
-
http://www.dedasys.com/davidw/Linux, Open Source Consulting
-
http://www.dedasys.com/
Locked
