[TYPO3-core] Commit message nitpicking...
steffen.gebert at typo3.org
Sun Feb 19 11:29:36 CET 2012
-----BEGIN PGP SIGNED MESSAGE-----
> The defined commit message format  distinguishes between "Fixes",
> "Resolves" for certain issue types and it allows "Releases" but not
> "Branches" for the targets. It's not much but still people (even Core
> devs) seem to run into the trap quite often and the nitpickers are happy
> to show them.
> 2) All other Folks - do we really need to distinguish between "Fixes"
> and "Releases" based on the context and are we really so square headed
> to forbid "Branches" as alias for "Releases"? Do we really want to make
> it so easy for the nitpickers? Are there technical reasons for that?
IMHO we don't need to distinguish between Fixes and Releases (it was
introduced at a later point, IIRC Ernesto).
I'm also fine with mixing Branches and Releases (however master is not a
BTW: Since yesterday, a first simplistic commit message check is running
on Jenkins (only checks a maximum line length of 74 chars).
I will continue with that the next few weeks and, of course, we can
discuss some of the rules, whether they're too strict or loose etc.
TYPO3 v4 Core Team Member
TYPO3 Server Administration Team Member
TYPO3 .... inspiring people to share!
Get involved: http://typo3.org
I work for TYPO3 solely in my spare time. If you think that
my work helps you running your business, you are invited to
send me a donation via PayPal to this email address. Thanks
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the TYPO3-team-core