On Aug 2, 2006, at 12:06 PM, Matt Hogstrom wrote:
Fine...I prefer a field in JIRA so I can execute a single query.
I'll assume the patches are in JIRA anyway and its a great place
for comments too :)
On Aug 2, 2006, at 12:08 PM, Sachin Patel wrote:
+1 [to jira]
On Aug 2, 2006, at 1:45 PM, Jason Dillon wrote:
I would rather see the community use JIRA to manage information of
this nature.
On Aug 2, 2006, at 1:47 PM, Joe Bohn wrote:
I agree. I'd prefer something that is directly integrated with
JIRA rather than [....]
On Aug 2, 2006, at 2:22 PM, Kevan Miller wrote:
As others have suggested, I think Jira's are the most appropriate
means for tracking RTC related Jira's.
On Aug 2, 2006, at 10:35 PM, Alan D. Cabrera wrote:
What about the changes to the Jira that we made a few weeks ago?
Ok, it took me a bit of work, but I think it will be worth it....
I've leveraged the work that Alan did with the new RTC Jira Workflow
and I also enabled the voting aspects already built into JIRA. No,
JIRA's voting capabilities don't capture the full range of +-1/0 that
can be expressed, but JIRA is not an official way to vote anyway so
who really cares :) Feel free to take it that extra mile if you have
the time and drive.
So I also hacked up a tool that will snarf all the data down, format
it with Velocity, and email it off to the dev list every Monday. For
good measure, it will also be generated and emailed to the scm list
on Tuesday, Thursday, and Saturday.
Totally flexible on how often and where we email it out.
The generated emails contain the appropriate disclaimers and
instructions for getting your patches an votes listed. Feel free to
suggest better/additional text.
-David
