> 1. When it comes to bugs that could possibly be closed, how are those > handled? For instance, with bug #4847, I updated the ticket with code and > comments and emailed the list. Is that the best method or is it spammy?
One of my frustrations with Trac is that its timeline view doesn't take into account any comments or attachments added to a ticket. Only closing or reopening a ticket seems to do that. So, it's easy to miss tickets that are very active comment-wise but were opened several months ago. If it isn't totally obvious that a ticket should be closed, I usually leave it open and defer to John, Ariel, and the others who can make the final call. Lately I've been trying to keep the tracker clean by closing tickets that have insufficient information and asking the OP to reopen when they can provide additional info. That way the reopened ticket will show up on the timeline and not be lost in the mists of Trac history. Here's the timeline view, btw: http://dev.jquery.com/timeline?daysback=7 > 2. For bugs such as #4849, I found that there is a narrow use case where the > conditions can be met. However, it almost feels like a judgement call > whether the core code should be altered or the bug closed. In this case, I > updated the bug - but I didn't email the list. Should I email the list to > further discussion or such items or, again, is this spammy? For those cases I would just add any useful information you can offer, such as whether you can repro the issue or perhaps a test case if one isn't already on the ticket. > 3. When reviewing the bug logs. My tendency is to look for things that > aren't assigned to anyone yet and try and clear those so I am not > duplicating work. I am hitting the below page. Is this the best way to go > about this? > > http://dev.jquery.com/query?status=new&status=assigned&status=reopene... That should be a good way to do it, but again don't think the priority there is the priority assigned by the jQuery team. Lately it has been quiet so most tickets aren't likely to have anyone working on them. Development is likely to get cranked up the next couple of months because jQuery usually has a big release in January of each year. > 4. For testing. > I did checkout the code from SVN. But when I reviewed the samples, I had > some questions / issues with the testrunner.js file. > ... > Would it be possible to update the DEV guide with more specifics around all > these questions? I can't answer these questions but will see if I can find someone who can. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
