incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carl Marcum <cmar...@apache.org>
Subject Re: Commit messages
Date Wed, 31 Aug 2011 01:53:54 GMT

On 08/30/2011 02:09 PM, Greg Stein wrote:
> The Apache Subversion codified and wrote up details on how the project
> should write log messages. This style has been in effect for its
> decade+ duration and has worked out very well. You may find it helpful
> for the (new) OOo log message guidelines:
>
>    http://subversion.apache.org/docs/community-guide/conventions.html#log-messages
>
> Cheers,
> -g
>
> On Tue, Aug 30, 2011 at 10:34, Shane Curcuru<asf@shanecurcuru.org>  wrote:
>> Some projects do this by convention within the committers, using various
>> tags within the log message to denote bug number, reporter, original source,
>> test id, whatever.  But it's up to each project to implement a policy for
>> this at the community level.
>>
>> There's a useful set of commentary on this kind of question here:
>>
>>   https://issues.apache.org/jira/browse/INFRA-3493
>>
>> Note also that SVN allows committers to update log messages after the fact,
>> so you can always add new annotations later if needed.
>>
>> - Shane
>>
>> On 8/28/2011 4:03 PM, Pavel Janík wrote:
>>>
>>> Hi,
>>>
>>> I do not know if Apache has some proposed syntax of commit messages (and
>>> don't have time to dig around it on the web), but I'd like to see commit
>>> log/messages containing the number of fixed issue referenced and no commit
>>> messages without that number.
>>>
>>> In OOo times, the commit logs were in the following structure:
>>>
>>> #12345#: Fix typo (i->y).
>>>
>>> Can we do the same/similar in Apache OpenOffice.org?
>>
>

I like the idea of starting from a something existing like the Apache 
Subversion guidelines and tailoring if needed based on Bugzilla needs etc.

Consistency is good especially for parsing with scripts.

Regards,
Carl

Mime
View raw message