[Development] the need to add a Task-Number in the release branch ...

Thiago Macieira thiago.macieira at intel.com
Thu Nov 14 17:46:16 CET 2013

On quinta-feira, 14 de novembro de 2013 13:27:42, Koehne Kai wrote:
> I guess what Ossi was wondering about was ' the commit message [should]
> state why this change belongs into the release branch' . It would be IMO
> weird to have sentences starting with 'This patch has to go into the
> release branch because ...' in the commit message. This reasoning (if it's
> not immediately clear from the commit itself) can happen in gerrit.

Don't write "this patch has to go into the release branch". Write instead 
"this change is important because" :-)

> In general I think we agree that any commit message in the release branch
> should get more attention than say in the dev branch, and that the rule
> should be 'if in doubt, create a JIRA task.'. But I'm also in favor of
> having this as a rule of thumb, instead of a hard rule.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131114/15015c5e/attachment.sig>

More information about the Development mailing list