On Friday 08 June 2007, Jeroen Ruigrok van der Werven wrote: > > -On [20070608 22:45], Eli Carter ([EMAIL PROTECTED]) wrote: > >It was suggested on IRC that there needs to be env-upgrade for this. > >Thoughts? > > I think it will save a lot of FAQ pointing. > > >I've also updated the default reports in db_default.py; they now reference > >the 'accepted' state instead of the 'assigned' state, but that's still not > >completely workflow independent. Even so, we probably want to leave it that > >way. > > Accepted seems a bit weird though still. It feels like a QA step which people > with triaging rights use to mark valid tickets from 'trash'.
True. But I was trying to "fix" the original workflow... without rewriting it completely. And the context within the graph shows it as being 'accepted' by the developer (whatever that happens to mean). I am open to changing the workflow completely to be something like simple-workflow, or some other suggestion. This is just as close to the original without being confused as I thought I could get. Eli --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
