On Sun, 28 Nov 2004 16:08:47 -0700, Larry Meadors wrote: >�Do we need to email out commit info?
Absolutely! >�This seems kind of extreme to me. Not in the least. All Apache projects do this, as do many SourceForge and other open source projects. By emailing the changelogs, we don't have to turn around and reiterate what we committed. Ideally, the commit logs should be a primary way that the developers communicate with one another. �We can explain what the code does when we commit it, and then the message is permanently attached to the change for future review. �I I can guarantee that once you've used this approach, you won't want to work any other way! >�If we do, can we make it a separate list? Yes. My bad. I neglected to remind everyone to subscribe to the <[EMAIL PROTECTED]>�list, which is where I should have posted the commit log. It is very important that all the committers subscribe to this list, and we should try to make each log entry read like a email you would post to the dev@ list. * <[EMAIL PROTECTED]> When applying a patch from a JIRA ticket, we should document the ticket and credit the submitter of the ticket. "Apply JIRA ticket 1234 "Something doesn't work, here's the fix" submitted by R. Favorite User." We can be more concise with the JIRA entries, since there is usually detail there that we lookup if needed, but we should still credit the submitter by name. -Ted.
