Re: [Ctags-devel] support request tracker

[Darren H. <dhi...@us...>]

Good ideas all around. I will implement both of these email address  
changes.

I don't understand the Elliot's command regarding the "visibility" of  
Support Requests. I made all Trackers open to each of the official  
maintainers.

I have been very sorry to have been unable to attend to so many  
issues in a timely manner.

Darren

On Jun 4, 2007, at 12:50 AM, Elliott Hughes wrote:

> i don't know how many people mail bugs directly to Darren, but if
> it's more than none, it might also be worth changing AUTHOR_EMAIL to
> cta...@li..., or not including an email address
> in the --version output.
>
> speaking of bug reports in unfortunate places, i've been going
> through the Debian bug database. Ubuntu doesn't seem to have any
> ctags bug reports, thankfully, and i wouldn't know where to look for
> other distributions. if anyone knows of any other collection of ctags
> bug reports, let me know!
>
>   --elliott
>
> On 2007-06-01, at 00:27, Elias Pschernig wrote:
>
>> On Thu, 2007-05-31 at 23:44 -0700, Elliott Hughes wrote:
>>> shall we change the visibility of the "Support Requests" tracker
>>> on the
>>> web site? i've just seen someone asked for help on there back in
>>> December, and if he'd mailed the mailing list we'd have probably
>>> fixed
>>> his problem six months ago, but as it is he's waited in limbo
>>> until now.
>>> the mailing list seems like the best place for support requests all
>>> round.
>>>
>>> as for the other trackers, should we change the "send email on new
>>> submission to address" field to ctags-devel rather than dhiebert?
>>> that
>>> should take some load off Darren, and mean (probably) quicker
>>> response
>>> times for submitters.
>>
>> For me, it would make sense. E.g. I only saw the last bug report  
>> about
>> the Python parser when you notified me (months after it was
>> submitted).
>> If an email notification would have been posted to the mailing  
>> list, I
>> could have responded immediately.
>>
>> -- 
>> Elias Pschernig <el...@us...>

--
Darren Hiebert
http://darrenhiebert.com