[Qgis-developer] Managing a future 2.18 or 3.0 documentation?

[Matthias Kuhn]

Hi Harrissou

On 07/20/2016 08:47 AM, DelazJ wrote:
> Hi folks,
> (sorry for the cross-posting)

being sorry doesn't make it any better ;)
honestly, I think in 99% of the cases it's fine to just target one or
the other.

> A few days ago, 2.14 doc has been released and the issues for 2.16 are
> being addressed now.

Thanks a lot for all your work on that!!

> 
> So questions:
> - Will we have a 2.18 (if ever) documentation?

I think it would be good to plan 2.18 in general. Triggering the release
scripts should be trivial. Since some features end up in 2.18, I guess
it will happen.
Concerning docs and also pre-release fixing, I wonder if this effort
should be spent on the 3.0 migration instead?

> - Are all features added to 2.18 also in 3.0 (and vice-versa)?

master_2 features should all also end up in master.
master features are not necessarily ported to master_2.

> - Should the webhook set different milestions according to the branch used?

Yes, master_2 => 2.18, master => 3.0.

Has there ever been a documentation released for 2.10 and 2.12?
If non-LTR get no documentation, there's probably not much point in
doing one for 2.18 I think?
People can still refer to the "testing" doc from master instead which
should match in many points (and where not, some notes can be included).

Matthias

> 
> [0] https://github.com/qgis/QGIS-Documentation/issues/1198
> [1] https://github.com/qgis/QGIS-Documentation/issues/1204
> 
> Regards,
> Harrissou
> 
> 
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>