[TYPO3-team-core-v5] Changelog considerations
Bastian Waidelich
bastian at typo3.org
Tue Jul 7 14:22:29 CEST 2009
Karsten Dambekalns wrote:
Hi,
>> Some questions though:
>
> Just to make sure, you saw the new section in the coding guidelines?
yes I did. But I had the feeling that they did not clearly answer my
questions. maybe i'm just too dump ;)
> Well, ~API is for public API changes. You might have ~BUGFIX touching
> the internal API, but no ~TASK with the commit. Clear? ;)
yes, it's getting clearer. thanks.
>> What if I'm committing a feature that adds a method to the API? [...]
>
> No, one line. Is what I wrote ("prefixed with one or more of the
> following codes") misleading or not clear enough? Anyway, I added this
> very example to the documentation...
Ok, I just wasn't 100% sure about the syntax. Now it's clear.
>> Maybe we should allow an additional type [NOTE] to be able to circumvent
>> the check then.
>
> Well, why rules when there are exceptions? I guess in any case TASK
> would be as good as NOTE.
I thought of administrative issues that are not code related, such as
setting svn properties etc.
But you're right, TASK should do..
Bastian
More information about the TYPO3-team-core-v5
mailing list