Difference between revisions of "Meetings/TripleO"
< Meetings
(→Agenda for next meeting) |
(→Weekly TripleO team meeting) |
||
Line 16: | Line 16: | ||
*# Another common reference on git commit messages http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html doesn't either | *# Another common reference on git commit messages http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html doesn't either | ||
*# In git's own git repo, 1.43% of commit messages in the last year ended in a period | *# In git's own git repo, 1.43% of commit messages in the last year ended in a period | ||
− | *# I'm not aware of any other OpenStack project which enforces this | + | *# I'm not aware of any other OpenStack project which enforces this |
+ | *# A hacking check to enforce "no period" - https://review.openstack.org/33789 | ||
* open discussion | * open discussion | ||
Revision as of 09:35, 20 June 2013
Weekly TripleO team meeting
MEETING TIME: Mondays at 20:00 UTC
Agenda for next meeting
Scheduled for June 10, 2013, 20:00 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130610T2000)
- bugs
- Grizzly test rack status
- CI virtualized testing progress
- Periods at the end of git commit messages. https://review.openstack.org/#/c/33262 (SpamapS, markmc)
- With the 50 char limit, space is at a premium on the first line
- The first line is often used as the Subject: in [PATCH] emails - subject lines in emails generally don't end in a period
- Examples in https://wiki.openstack.org/wiki/GitCommitMessages#Summary_of_GIT_commit_message_structure don't end in period
- Another common reference on git commit messages http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html doesn't either
- In git's own git repo, 1.43% of commit messages in the last year ended in a period
- I'm not aware of any other OpenStack project which enforces this
- A hacking check to enforce "no period" - https://review.openstack.org/33789
- open discussion