Hi,
Given that there is already a long queue to deal with in Doc repo (with two
releases without documentation), it would be nice if the next QGIS release
number is automatically tagged on the issue. It'll prevent writers to add
documentation about 2.14 features while writing 2.12.
2015-11-27 9:57
Hello,
Some request, question:
1) A new request (or not): what if the code is reverted? Is it possible to add
a comment in the document ticket?
2) About the new tag "Need docs": do we really want a new tag instead of just
changing the tag to [Documentation] which could just mean "We need to do
Currently the hook seems broken, I'll try to fix it this afternoon/evening.
Happy to do add the 'needs docs' tag too. Is this already a tag? Just
sent me the exact tag text, and the type of issue that you want me to
make for it in Documentation issue-list.
Matthias had also a feature request:
ht
Nyall, that would be useful. And GUI changes as well. In Docs we have tags
for identify the need to create new screenshots for users manual.
DelazJ escreveu no dia qui, 26/11/2015 às 23:06:
> Hi,
> BTW, it's not against Documentation repo but could this also be used to
> fetch bug fixes so that
Hi,
BTW, it's not against Documentation repo but could this also be used to
fetch bug fixes so that a list of bug fixes can be generated to accompany
qgis releases?
2015-11-26 22:40 GMT+01:00 Nyall Dawson :
> Hi all,
>
> Just a thought I had - could the new hook which creates a documentation
> is
Hi all,
Just a thought I had - could the new hook which creates a documentation
issue when the message contains "feature" be amended so that it detects an
additional "needs docs" tag too?
My thoughts are that sometimes a change should be accompanied by
documentation updates but isn't a new featur
