On Jan 19, 2007, at 6:00 AM, Jeremy Whitlock wrote:
Hi All,
Sounds good to me. I'll give this a little thought, craft an
email, get
your approval and then send it.
You don't need my approval to send it. In fact, I recommend you just
hack your ideas right into the wiki and see where it takes you.
-David
Take care,
Jeremy
P.S. - If I can help with any JIRA reporting, let me know. At
CollabNet, I
do many scripts/tools that do this type of thing.
On 1/18/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Jan 18, 2007, at 9:54 PM, Alan D. Cabrera wrote:
>
> On Jan 18, 2007, at 11:52 AM, Jeremy Whitlock wrote:
>
>> I was wondering if we had patch submission guide lines? If we
>> do not,
>> can we put some together. Now that I'm getting more involved in
>> OpenEJB
>> (finally) I would like to make it easier on developers to be
able to
>> identify patch requests on the mailing list. I know we have Jira
>> to house
>> the issues and the patch contents but usually you get an email
>> asking for
>> someone to review/apply a patch and since there is no particular
>> format for
>> the request, it is hard to make sure you don't miss a request.
>> I'm not sure
>> we need a real process but maybe just a suggested email subject
>> line that
>> jumps out to us developers so we don't overlook a patch review/
>> application
>> request. Thoughts?
>
> Someone on the OpenEJB team is really, really, good at writing
> automatic jobs that run Jira reports and sends mail to dev lists.
> I wonder if we could have one that lists ready patches that haven't
> been picked up by a committer. Hmmm, his name escapes me...
He sounds like an outstanding guy. But seriously, Alan, you should
brag like that in public. I've never known those sleep statements to
do any of the things you describe :)
There's a report that goes out to the scm list once a week of open
issues with patches. Does that fit the bill?
-David
