[Qgis-community-team] [Qgis-developer] new commit label: [NEEDS-DOCS] for QGIS commits will also raise an issue in QGIS-Documentation

[Richard Duivenvoorde]

Hi Harrissou,

yes, I'll have a look into it as soon I find time. By the way, the
webhook we run is:
https://github.com/qgis/QGIS-Sysadmin/blob/master/webhooks/github_feature_tracker.cgi
(and ran in /usr/lib/cgi on qgis server)

So I'll see that I add a milestone to all issues I generate now.

Which milestone for now?

That would be 2.14 or 3.0?
(I think current 2.14 will be the last 2.x docs for now, but I'm ok with
both options)

Regards,

Richard




On 21-04-16 10:28, DelazJ wrote:
> Hi all,
> 
> Richard, given that new reports belong to the next release, would that
> be possible to automatically set the milestone when generating the
> report? It will help filtering the list (and avoid some manual changes).
> 
> Regards,
> H.
> 
> 2016-02-18 11:51 GMT+01:00 DelazJ <delazj at gmail.com
> <mailto:delazj at gmail.com>>:
> 
>     Thanks guys for the reminder.
>     And if some features are missing, I think we'll find them while
>     writing about another feature or using QGIS.
> 
>     2016-02-18 7:17 GMT+01:00 Otto Dassau <otto at qgis.org
>     <mailto:otto at qgis.org>>:
> 
>         Am Wed, 17 Feb 2016 21:22:57 +0100
>         schrieb Yves Jacolin <yjacolin at free.fr <mailto:yjacolin at free.fr>>:
> 
>         > Le mercredi 17 février 2016, 19:53:54 Richard Duivenvoorde a écrit :
>         > > On 17-02-16 19:42, DelazJ wrote:
>         > > > To have a complete list of issues for documentation (especially for
>         > > > needs_docs tag), does it mean that developers should amend their
>         > > > previous commits message (don't know if it's doable)  so that a grep
>         > > > can retrieve these commits? Or do we consider that they are "lost"
>         > > > improveme
>         > >
>         > > Well, not sure if that is technically possible: it means changing the
>         > > commit message by adding a label AND writing some prose about the
>         > > addition. But dev's feel free to add the label if possible, or else:
>         > > sent an email to the documentation team describing what you fixed/added
>         > > to excisting features :-)
>         > >
>         > > Regards,
>         > >
>         > > R
>         >
>         > Harrissou,
>         >
>         > Note that this is only true for 2.14 release as I copy pasted the commit
>         > message into each issue for 2.10 and 2.12. Batch script was up for 2.14.
>         >
>         > But if I remembered correctly, Otto did a check for 2.14.
>         >
>         > Y.
> 
>         yes, I did that until 2.14 feature freeze and hope I got/added
>         all issues
>         for the documentation.
> 
>         Regards,
>         Otto
> 
>         _______________________________________________
>         Qgis-community-team mailing list for organizing community
>         resources such as documentation, translation etc..
>         Qgis-community-team at lists.osgeo.org
>         <mailto:Qgis-community-team at lists.osgeo.org>
>         http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> 
> 
>