Committers Call 2011-02-07
Attendees
Edwin Shin
Matt Zumwalt
Molly Pickral
Simon Lamb
Garrick Van Buren
Agenda
- New Cucumber Rake Tasks
- Hudson
- Git commit messages
- Project updates
Notes
New Cucumber Rake Tasks
Default to core+local
Document in source tree
Hudson
http://hudson.projectblacklight.org/hudson/
Bess was working on getting Hydrangea.
Git commit messages
Commit messages should follow the guidelines described in detail at http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html.
In summary:
- First line: JIRA issue ID in all caps (if applicable), followed by a brief description (~ 50 characters)
- Second line: blank
- Following lines: more detailed description, line-wrapped at 72 characters. May contain multiple paragraphs, separated by blank lines. Link to the JIRA issue, if applicable.
Use the present tense when writing messages, i.e. "Fix bug, apply patch", not "Fixed bug, applied patch."
Sample commit messages
- linked to a JIRA issue:
FCREPO-780: NPE thrown on disseminations Fix for the following bug: Fedora throws a null pointer exception if you call a disseminator that fronts a web service whose response does not contain a "Content-type" header. https://jira.duraspace.org/browse/FCREPO-780
- Minor Commits accumulating against a single ticket/story:
FCREPO-780: Fixed a typo in model spec. https://jira.duraspace.org/browse/FCREPO-780
etc. etc.FCREPO-780: Adjusted padding for inputs https://jira.duraspace.org/browse/FCREPO-780
Project Updates
- Hull