[QGIS-Developer] Documentation and algorithm news

[delazj at gmail.com]

Hi, 
Le 15 mars 2018 12:53 PM, matteo <matteo.ghetta at gmail.com> a écrit :
>
> Hi Alexandre,
>
>
> > My suggestion is:
> > 
> > - Keep the branching as it is. That is, branch and release only for QGIS
> > 3.4 LTR
> > - Keep updating the master branch for all 3.x features (if possible giving
> > priority to 3.0 features)
> > - Backport anything missing on 2.18, if applicable.
> > - For changes (in processing or not) specific to 3.2 or 3.4 add a note
> > saying "New in QGIS 3.2" (we could use a substitution for easy tracking).
> > That way, a QGIS 3.0 user using Testing Documentation understands that the
> > feature/parameter or whatever is not yet available for him. (This is how
> > Sphinx documentation does)

This is exactly what i had in mind as a system

> > - Before the release of QGIS 3.4 Documentation, we clean up all those
> > messages.
> > 
> > IMHO, this methodology will keep the simplicity of the process, while
> > allows to document recent changes while they are still fresh.
> > 
Agreed. 

> > About the ALGCHANGE, it's a +0 for me. I would prefer to keep it as simple
> > as possible and try not to have too many tags, The processing one would
> > with the risk that Developers.
>

For information, I assigned all issues updating or creating an alg help to Matteo. Not all the Processing issues… yet ;) 

> always thinking aloud (really thinking aloud).. what about branching the
> docs but having a *dynamic* system based just on sphinx .. include:: ? I
> mean, branching the 3.2 release and having the correct index set up with
> just the Processing docs?
>
Fail to see the system but i'm not used to this Sphinx role. 

Regards, 
Harrissou


> Cheers
>
> Matteo
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer