kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #31842
Re: New feature notifications
-
To:
<kicad-developers@xxxxxxxxxxxxxxxxxxx>
-
From:
Maciej Sumiński <maciej.suminski@xxxxxxx>
-
Date:
Wed, 22 Nov 2017 16:16:16 +0100
-
Authentication-results:
spf=pass (sender IP is 188.184.36.50) smtp.mailfrom=cern.ch; lists.launchpad.net; dkim=none (message not signed) header.d=none;lists.launchpad.net; dmarc=bestguesspass action=none header.from=cern.ch;
-
In-reply-to:
<3b5ff84f-0d49-5eb6-6d72-16c83c7efccf@gmail.com>
-
Spamdiagnosticmetadata:
NSPM
-
Spamdiagnosticoutput:
1:99
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
On 11/22/2017 03:55 PM, Wayne Stambaugh wrote:
> On 11/22/2017 08:55 AM, Maciej Sumiński wrote:
>> On 11/22/2017 02:48 PM, Marco Ciampa wrote:
>> [snip]
>>> Please please please,
>>>
>>> when some new feature is accepted (code merged in master branch), either
>>> write it in the dev (master) branch of the documentation or somewhere to
>>> enable doc writers to describe the new feature... (wiki? txt in the
>>> source code? Bug Report?)
>>>
>>> I think that a simple description in a bug report is the easiest way to
>>> assure that new features get correctly described in the docs.
>>> Parsing dev ml messages for these "hints" is IMHO unmanageable...
>>>
>>> TIA
>>>
>>
>> Hi Marco,
>>
>> I thought we are supposed to use tags in commit messages (NEW, CHANGE)
>> [1]. I can create a bug report in the documentation repository, if this
>> is the preferred way. If so, then I suppose it should be made a policy.
>
> You are and you did. Nice job! The real question is how does this
> information make it from the source repo commit messages to doc devs so
> the docs can be updated accordingly?
For example:
git log --grep="CHANGE[D]\?:\|REMOVE[D]\?:\|NEW:"
I can turn it into an alias and add it to the same files that handles
'git fixes' command. You can also extend the query with a date or a
commit hash. This way, once you enable the git alias configuration you
may type:
git changelog --since="1 Jan 2017"
or
git changelog 527c6f001
>>
>> I am afraid it might be hard to follow for occasional patch submitters,
>> should it be the committer responsible for creating a bug report?
>>
>> Regards,
>> Orson
>>
>> 1. https://git.launchpad.net/kicad/commit/?id=527c6f0014b03
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help : https://help.launchpad.net/ListHelp
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References