Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4E5D9432.9010201@apache.org>
Date: Tue, 30 Aug 2011 21:53:54 -0400
From: Carl Marcum <cmarcum@apache.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Lightning/1.0b3pre
 Thunderbird/3.1.12
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: Commit messages
References: <E43CEDE7-723E-4499-A59E-A12956F9C66D@Janik.cz>
	<4E5CF4F6.3040909@shanecurcuru.org>
 <CABD8fLVgwKDr=hNP1mdbcWwuZrgN4K7Z-84wmk3x2r7JV+P5oQ@mail.gmail.com>
In-Reply-To: 
 <CABD8fLVgwKDr=hNP1mdbcWwuZrgN4K7Z-84wmk3x2r7JV+P5oQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


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