Closing tickets at triage

[Jeroen van Dongen]

While browsing through the open, unreviewed tickets I encountered some
tickets like 1049 (http://code.djangoproject.com/ticket/1049) which
imo should be closed/rejected for various reasons. In this case:
1) the topic of the ticket is oldforms, which will be phased out soon
(hence it is unlikely that any of the core developers wants to spent
resources on it unless it's a really horrible bug pestering many -
which it apparently isn't, see points 2 and 3)
2) the ticket is a year old
3) there's a perfectly fine workaround (just use a normal view
instead of a generic view in the given case)

There are more tickets like this, I also suspect that there are
tickets which are unreviewed and open, yet quietly solved or otherwise
no longer relevant as part of the ongoing improvements and changes
made to Django.

However, there is no "reject" option in the triage stage. One can only
accept it, or ask for a design decision. What is the correct way to go
with this kind of tickets?
1) accept it and close it as 'wontfix'
2) ask for a design decision
3) add a "reject" option so that they can be rejected at triage time
4) ...

Please advise - I'd like to do some weeding in the garden of
tickets ;-)

[Jacob Kaplan-Moss]

On 2/26/07, Jeroen van Dongen <baasb...@gmail.com> wrote:
> There are more tickets like this, I also suspect that there are
> tickets which are unreviewed and open, yet quietly solved or otherwise
> no longer relevant as part of the ongoing improvements and changes
> made to Django.
>
> However, there is no "reject" option in the triage stage. One can only
> accept it, or ask for a design decision. What is the correct way to go
> with this kind of tickets?

The "stage" option isn't required, so the right thing to do is just to
mark tickets of this nature INVALID or WONTFIX.

Jacob