Hi!
It seems that I have forgotten to send my reply to the mailing list...
matteo escreveu no dia sexta, 16/03/2018 às 08:38:
> Hi Alexandre,
>
> > Maybe I am missing something, why would lose the information? Because it
> > has not been released?
>
>
> I mean that if
Hi,
Le 15 mars 2018 12:53 PM, matteo 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
> >
Hi Alexandre,
> I have to agree with Harrissou. Going back to branch documentation at each
> point release will not help, it will only create a bigger burden to a very
> small team of interested people, with lots of commits needing to be ported
> back or forward.
>
> Although I have proposed to
Hello all,
I have to agree with Harrissou. Going back to branch documentation at each
point release will not help, it will only create a bigger burden to a very
small team of interested people, with lots of commits needing to be ported
back or forward.
Although I have proposed to branch 3.0
Hi Harrissou,
> Does it mean that current testing becomes 3.0 and testing targets 3.2?
> When will the doc branched? As soon as the application is released?
> Because of the low level of man power in doc writing, we decided to have a
> LTR based release plan. Plan we struggle to follow. With the
Hi,
Thanks Matteo and Richard for having brainstormed on this issue and for your
outcome. And sorry to not have joined you.
Bear with me but i am less enthusiastic with some of the proposals for the
reasons below
> On 03/14/2018 10:29 AM, matteo wrote:
> > Hi all,
> >
> > in the last weeks
Thanks Matteo and Richard,
This sounds like a very good path forward. Having up-to-date
documentation in this area is crucial and this approach with branching
and tagging sounds like a very good workflow to me.
This mainly depends now on developers to provide enough context and
proper tagging of
Hi all,
in the last weeks I've pointed out some problems we can have we the
documentation, so, together with Richard, these are the conclusions:
* documentation repo will be branched together with QGIS release
* having these branches allows doc writers to update QGIS but,
especially, Processing