[Qgis-community-team] manual 1.8 as html and pdf

[Tim Sutton]

Hi

On Sat, Jan 5, 2013 at 11:54 PM, Richard Duivenvoorde <richard at duif.net> wrote:
> On 05-01-13 16:49, Otto Dassau wrote:
>
>> Apart from the update, we are still about to improve the infrastructure
>> and
>> translation environment. And of course we need to update content for the
>> next release, which will provide again a lot of new features.
>>
>> As a next step I will create a branch for the translations next week so we
>> can move on updating to the next version in master.
>
>
> Hi Otto,
>
> great, thanks for all the work!
>
> Do we already have a plan how to work it out in the documentation process?
>
> As you proposed in an earlier webmail, we can start with a branch of current
> repo. Which actually is both the website and a documentation part.
> Only the documentation part (of this 1.8 branch) should be 'frozen', and
> deployed in some kind of 1.8 branch/uri in the docs website. The website
> part of the master-repo will evolve further in our 'normal' website?
>
> OR should we just copy the User Manual directory in a 'User Manual 1.8'
> directory in current master? It is not very 'gitty', but I think it should
> be ok and more 'natural' because it is only the 'User Manual' which is
> really version bound?
>

my opinion is that we should make a branch per version. If you make
directories rather its going to be hard to merge upstream/downstream
changes into master.

Regards

Tim

> What do real admins think of this?
>
> Regards,
>
> Richard
>
>
>
>
> _______________________________________________
> Qgis-community-team mailing list
> Qgis-community-team at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team



--
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==============================================
Visit http://linfiniti.com to find out about:
 * QGIS programming services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux Irc: timlinux on #qgis at freenode.net
==============================================