[dev] [commits] Horde branch master updated. content-1.0.0alpha1-55-g737d6d8
Michael M Slusarz
slusarz at horde.org
Fri Mar 11 20:03:14 UTC 2011
Quoting Jan Schneider <jan at horde.org>:
> Zitat von Gunnar Wrobel <wrobel at horde.org>:
>
>>
>> Zitat von Jan Schneider <jan at horde.org>:
>>
>>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>>
>>>> -----------------------------------------------------------------------
>>>>
>>>> commit 737d6d89ed710f103e20385dfe7daf76d2869d34
>>>> Author: Michael M Slusarz <slusarz at curecanti.org>
>>>> Date: Thu Mar 10 16:46:33 2011 -0700
>>>>
>>>> changelog
>>>>
>>>> imp/docs/CHANGES | 2 ++
>>>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>>
>>> Please update package.xml too.
>>
>> I still intend to provide a commit helper within the components
>> tool that would enter the commit message as a note to the changelog
>> (or the changelogs in case we intend to have two for the
>> applications). I hope to get that done at the beginning of next
>> week. If you have any wishes concerning that... I'm open to
>> suggestions.
>
> I'm not sure how you intend this to work. Mark changelog entries
> specially in the commit message? We definetely don't want all commit
> messages in the logs. Also, which changelog is being updated when
> several components are affected?
Sounds like Gunnar is working out the details of his solution. But I
am NOT going to manually enter entries into both CHANGELOG and
package.xml. You are asking for *3* separate descriptions for a
commit (the commit message itself, CHANGELOG, and package.xml). We
should be writing 1, or at most 2, messages. Adding yet another place
to maintain this information is a giant step backward.
Either CHANGELOG needs to be automatically generated from package.xml
or vice versa. At a minimum, we should chop all old CHANGELOG entries
anyway (e.g. H3 and previous), or at least move these changes to a
different file (CHANGELOG.OLD).
michael
--
___________________________________
Michael Slusarz [slusarz at horde.org]
More information about the dev
mailing list