72 hours are not enough for maintainers?
Ryan Schmidt
ryandesign at macports.org
Fri Feb 22 05:22:02 PST 2008
On Feb 22, 2008, at 07:18, js wrote:
> On 2/22/08, Ryan Schmidt wrote:
>
>> On Feb 21, 2008, at 11:31, Eric Hall wrote:
>>
>>> I'd like to see an improvement in maintainer notification,
>>> some way for trac to grok the maintainers of a port a ticket is
>>> filed
>>> against and send them an email without having a human properly
>>> assign
>>> the ticket or fill in the CC: field. I have no idea if there are
>>> even
>>> hooks in trac to make that possible....
>>
>> I suggested that before too, but then jmpp pointed out that we don't
>> capture the information "what port is this ticket for?" anywhere in
>> the ticket. We don't have a field for that. Many people put the
>> affected port name somewhere in the ticket title, but many don't,
>> and
>> those that do don't always put it in a consistent place. I don't
>> know
>> if we can reliably just try to find any portname in the ticket
>> title.
>> Also, many reporters report problems against the port they're trying
>> to install, rather than against the dependency which actually
>> failed.
>
> I suggest giving non-maintainers the permission to change "Assigned
> to" field.
It seems to me like that would be a good idea too. But I'm not sure
what all the implications of that would be.
> Once tickets are properly assigned, all you have to do is to look at
> "My tickets".
Assuming reporters assign tickets correctly, sure.
> In addition to that, How abount sending reminder to macports-dev
> when there're tickets unchanged more than a few weeks?
> Trac's backend is RDBMS so checking ticket state should be easy.
I know I have old tickets. Some need planning, some are waiting for
upstream fixes, some are not very important but are still open
because they're still unresolved. I don't need lots of emails nagging
me about these. I have enough of an email problem as it is. Also,
macports-dev is not a place to send automated emails; it's a place
for discussing the development of MacPorts. For automated mails we
have other lists, like macports-changes and macports-tickets.
More information about the macports-dev
mailing list