[TYPO3-core] Commit message nitpicking...

[Steffen Gebert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Tolleiv,

> The defined commit message format [1] 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
release..).

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.

Kind regards
Steffen

- -- 
Steffen Gebert
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/

iQEcBAEBAgAGBQJPQM8QAAoJEIskG/rSlyw4nhcH/jy74ch9+oHuPZlDNEc0ndqq
VF7sFzEKtqJcHggZ3nAv0D83aihOLmmH5rxtUPv2RgGJnY2cPRsay6IVqBvGls5k
R+y0ml2/fI9qFLdE/MqXrr7IW3RsSbraIVyJVHk40vzDetKYQE06Vq9Lq2vWDzQg
rObzph3soo+DPjWPqtheFD5ndNeqwGpDfmIZ9BUvtM0+qqrT0039OfKMX2aTxRrR
KWbUnnsi8GSfVukrgNGCKf7HfJEUzk/7KWrsrduqhtlDxFPDgYDCnGRSx/w+Yvqv
LTqRZvY8Uzn3fcJdGk4njKE0C1zmEF+nmyLzTMNR1Kbmvo+a0ErU0xOnT9O5aQE=
=+URH
-----END PGP SIGNATURE-----