[development] Updated closed issues

[Neil Drumm]

When you are doing this, please
1. Test the issue in CVS HEAD to see if it is still relevant and reproducible.
2. Think about where the issue actually belongs. Usually 7.x-dev is
the right version; we fix things in CVS HEAD, then backport. Look over
other settings:
- Is it really a support request?
- Is the category otherwise correct?
- Is there enough information to proceed?
- If marked critical, is it really something that fundamentally breaks
some part of Drupal for many people?
- Is the component correct?
3. Write an informative note about the change, for example, "x.y.z is
a deprecated version. Features are only added to the development
version, which is currently 7.x. I agree that it would be a good
additon to Drupal core."

We always keep the highest-priority queues in the "Contributor links"
block, which you can enable when editing your account. Please consider
looking over those queues as well. I, of course, would like to see
people reviewing 5.x issues too.

On Mon, Apr 7, 2008 at 3:27 AM, Fernando Silva <fsilva.pt at gmail.com> wrote:
> Hi,
>
>  I want to ask Drupal.org maintainers to update closed bugs (closed,
>  duplicate, wont fix, etc) which have version "x.y.z" to another
>  version. Ideally, it should be moved according to the issue last
>  update, but to simplify things it can just be updated to 6.x-dev.
>
>  Thanks,
>   Fernando
>
>  PS: "x.y.z" issues has only 6 pages, meaning that it can be removed
>  very soon from the version option list.
>



-- 
Neil Drumm
http://delocalizedham.com