[Qgis-community-team] Branching 2.8 docs?

[Alexandre Neto]

Hello all,

I will start reviewing and updating the screenshoots as soon as possible.

Best regards,

Alexandre Neto

On Tue, Mar 3, 2015 at 2:44 PM, Larissa Junek <junek at gbd-consult.de> wrote:

> Am Tue, 3 Mar 2015 09:59:53 +0100
> schrieb Otto Dassau <dassau at gbd-consult.de>:
>
> > Hi,
> >
> > Am Tue, 3 Mar 2015 10:44:14 +0200
> > schrieb Alexander Bruy <alexander.bruy at gmail.com>:
> >
> > > Hi all,
> > >
> > > What is current status of the 2.8 documentation? Seems with LTR
> > > release we need to review our workflow and branch LTR documentation
> > > in same time as QGIS branched.
> >
> > Larissa is currently working on the documentation update in master. I
> > don't know if others, too? Once it is in status 2.8 we could create a
> > translation branch as usual.
> >
> > > If we stick with previous workflow when documentation update is
> > > done in master it is impossible to document new features, available
> > > in upcoming non-LTR releases
> > > until LTR documentation is ready. For example I'm about to commit
> > > into QGIS updated TauDEM Processing provider and also want to update
> > > corresponding entries in User Guide. But current documentation
> > > master is still for 2.8.
> > >
> > > Maybe we should branch 2.8 documentaton and continue to update it in
> > > branch. This allow developers and volunteers to update master
> > > branch by adding information
> > > about new features.
> > >
> > >Opinions?
> >
> > If we branch now, before all 2.8 features are documented, we will
> > have to do the work twice - in 2.8 branch and in master. I would
> > prefere that we focus on updating 2.8 first, then branch and add new
> > features beyond 2.8 into master again.
> >
> > Because AFAICS there is not too much work for 2.8 left, mainly print
> > composer and a general check, because there are quite a lot gui
> > changes we should update.
> >
> > Regards
> > Otto
> > _______________________________________________
> > Qgis-community-team mailing list for organizing community resources
> > such as documentation, translation etc..
> > Qgis-community-team at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
>
> Hi all,
> I agree with Otto, that work shouldn't be done twice.
> I updated the 2.8 until today . Actually when having a look at the
> developers commits (for example on the Manual Tasks List) new features
> in the Print Composer have to be inserted and Features described on
> http://changelog.linfiniti.com/qgis/version/2.8/ have to be considered.
>
> I would like to ask the community if there are people that can work on
> the 2.8 documentation master so that we can branch afterwards and have
> a beginning for the upcoming non-LTR releases.
>
> Kind regards,
> Larissa
>
> _______________________________________________
> Qgis-community-team mailing list for organizing community resources such
> as documentation, translation etc..
> Qgis-community-team at lists.osgeo.org
> http://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/20150303/fb8705c2/attachment.html>