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 - Even is the feature is for developers, try to write something understandable for non developpers - Link to a more detailed resource (blog post, QEP, detailed PR) instead of writing long entries - Think also to ease the work of translators Cheers ! 2018-02-27 8:14 GMT+01:00 Richard Duivenvoorde <[email protected]>: > 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 > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
