Hi
I'm also +1 for a more described commit: things have improved this last
year but still some "Unfortunately this naughty coder did not write a
description... :-("
2018-02-27 10:36 GMT+01:00 Etienne Trimaille <etienne.trimai...@gmail.com>:
> Just a quick note, I think I will deploy some updates (and some fixes !)
> on the changelog.qgis.org in 1 hour and 30 minutes. So don't edit around
> that time. Thanks
>
> 2018-02-27 11:42 GMT+03:00 Régis Haubourg <regis.haubo...@gmail.com>:
>
>> Hi, +1 with Richard.
>> I spent some hours polishing the changelog on Sunday and the task is
>> huge, I'll try to continue tonight.
>>
>> Maybe also we should explicit some tips:
>>
>> - Use Markdown syntax for a more readable changelog
>>
>
markdown or restructuredText? I'd think that plain text is much better...
> - Even is the feature is for developers, try to write something
>> understandable for non developpers
>>
>
Oh yes, please!!!!!!
> - Link to a more detailed resource (blog post, QEP, detailed PR) instead
>> of writing long entries
>>
>
I do not feel that long entries are bad. You do not have to click here and
there to find more information and see the global picture: all is there in
one place. all is then needed is to copy-paste and clean/adapt to the
context.
Thanks to all those involved in changelog writing; it'll be of real help to
the documentation.
Regards,
Harrissou
- Think also to ease the work of translators
>>
>> Cheers !
>>
>> 2018-02-27 8:14 GMT+01:00 Richard Duivenvoorde <rdmaili...@duif.net>:
>>
>>> On 26-02-18 23:51, Nathan Woodrow wrote:
>>> > Hey all,
>>> >
>>> > The changelog page for 3.2 is now active. Would be good if we can
>>> start
>>> > adding entries as we make changes so we don't have to wait until right
>>> > at the end like 3 :)
>>> >
>>> >
>>> > http://changelog.qgis.org/en/qgis/version/3.2.0/
>>>
>>> Thanks Nathan,
>>>
>>> good idea.
>>>
>>> @allDevs: please add some (preliminary) text (and if possible picture
>>> there there) for every new feature you code.
>>>
>>> OR
>>>
>>> In case of a new feature a new issue is automatically created here:
>>> https://github.com/qgis/QGIS-Documentation/issues and tagged 'QGIS 3.2'
>>> Please always add some information/screenies/hints for doc writers when
>>> you add a new feature. It is MUCH more efficient if a doc writer can
>>> take some text and rewrite it, then guessing what the new Feature was
>>> and is forced to ask the dev halve a year later...
>>>
>>> Regards,
>>>
>>> Richard Duivenvoorde
>>> _______________________________________________
>>> QGIS-Developer mailing list
>>> QGIS-Developer@lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>>
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
