I like this idea for an additional reason:
I look at the Django timeline regularly, but I have ticket detail
changes filtered out. Therefore I *don't* see changes like
"unreviewed" -> "accepted", etc. I do, however, see ticket status
changes (closing, reopening, etc.). Thereby these kinds of changes
will be more visible, especially when a ticket is re-opened,
presumably with more information.
I do have one concern, though... I worry that it might be off-putting
to new contributors who may not provide enough information if their
ticket is *closed* with needsmoreinfo rather than commented on with
"needs more info".
All in all, I like it.
- Gabriel
On Nov 13, 11:58 am, SmileyChris <smileych...@gmail.com> wrote:
> On Nov 14, 5:52 am, Daniel Moisset <dmois...@machinalis.com> wrote:
>
> > In most cases we sent a reply back
> > to the submitter asking for more details about their problem, but the
> > ticket remains in the "Unreviewed" state, still taking the time of
> > other triagers looking for tickets to review.
>
> > Many projects have a "need information" state to report this
> > situation. I think adding this to the ticket state diagram [1] would
> > be helpful for triagers, and to developers reviewing the ticket list
> > and wanting to know how many tickets actually need to be looked at
> > before a release.
>
> > What are the thoughts of the core team on this?
>
> Here's another more forward solution, requiring less follow-up
> triaging:
> Have a "needsmoreinfo" resolution. Tickets can be closed with that
> with a note to reopen it when more info is provided.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
