[asterisk-dev] [policy] Bug Tracker Workflow Discussion
Carles Pina i Estany
carles at pina.cat
Mon Aug 11 12:03:21 CDT 2008
Hello,
On Aug/11/2008, Jay R. Ashworth wrote:
> On Mon, Aug 11, 2008 at 10:07:26AM -0400, Leif Madsen wrote:
> > RESOLVED: A resolution for this issue has been reached. This issue
> > should immediately be CLOSED.
> >
> > CLOSED: No further action is necessary for this issue.
>
> I'd just like to ride my personal hobby horse about ticket trackers
> here:
>
> Anyone can "RESOLVE" a ticket.
>
> Only the *originator* should be able to "CLOSE" one. Nothing pisses
> me off worse than someone closing my ticket when I don't think they're
> done fixing it; telecom carriers are famous for this.
If you are in the other side (telecom carrier for example) sometimes is
"impossible" that some user closes the ticket.
I would just add a defined timeout to say: if Asterisk developer
says that it's fixed, ask to the reporter and reporter says nothing in 2
weeks, let's assume that "no news, good news" :-) and close the ticket.
Just my thoughts/experience.
--
Carles Pina i Estany GPG id: 0x17756391
http://pinux.info
More information about the asterisk-dev
mailing list