[Qgis-community-team] documentation - issue #3872 3.10 label

[DelazJ]

Hi Larissa

Le ven. 25 sept. 2020 à 14:13, Larissa Junek <l.junek at gmx.net> a écrit :

> Hi folks,
>
> I have a question concerning the backport for 3.10 LTR in documentation.
>
> Issue #3872 is for LTR documentation. I wanted to describe the new
> functionality and I see there is a description I think in qgis testing.
>
> Could you provide the url (and quotes) of the sections in the docs that
bother you, please? It would help visualize the issue.

Is it possible to remove the information describing the QGIS testing
> version so tha it's correct for QGIS LTR?
>
> Is the information in the testing doc wrong for QGIS 3.15? If not, I can't
see why we'd need to remove it. Or do you mean that there is information
about testing features in the 3.10 LTR docs?
Generally speaking:
- 3.10 and testing are two separate docs, with their respective branch
(release_3.10 and master). This means that they are expected to diverge at
some point and they don't depend on each other.
- Providing a 3.10 fix doesn't necessarily have to go through the workflow
"add to master --> enable backport --> merge in master --> merge in
release_3.10". That process is just for convenience, when texts are
identical. If things are different, you better directly write your PR
against the release_3.10 branch
- But, unless the feature has in the meantime being removed from QGIS, it's
expected that the change you add directly to 3.10 is forward pushed to
master also

Regards,
Harrissou

This will be important for me since from the end of October I will
> document the new QGIS LTR.
>
> Cheers, Larissa
>
>
>
> _______________________________________________
> Qgis-community-team mailing list for organizing community resources such
> as documentation, translation etc..
> Qgis-community-team at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-community-team/attachments/20200925/dbe2b249/attachment.html>