I acknowledge that sorting out the documentation stuff in the different versions is a lot of work.
However: In the enterprise environment there is always a certain lag between the newest version and the version which is actually in use. Many customers I know will require up to 24 months time until they upgrade.
This means that 1.7 based svn tools will be in wide usage a long time after the release of 1.8. And all those users would be happy to have an accurate documentation.
So do you see any chance to provide an updated documentation for 1.7 ?
> On 27 March 2013 13:02, Simon Large <simon dot tortoisesvn at gmail dot com> wrote:
> > On 27 March 2013 11:09, walter klust <wklust at elego dot de> wrote:
> > > Can I get information when the next update of the documentation is
> > planned ? There are some changes in nightly which should be official.
> > I'll try to make time for it over the Easter break.
> OK, I have had a look and there are 76 revisions changing the docs since
> 1.7 was branched. Some of those changes refer back to 1.7, but many refer
> to 1.8. Merging the 1.7 changes only is going to be hard, and to be honest
> there is unlikely to be another 1.7.x release after the one this coming
> week, which I have already missed the tag for. So I think the best plan is
> to leave 1.7 as it is, and when 1.8 is released start merging any necessary
> doc changes in trunk back into the 1.8 stable branch.
> : ___
> : oo // \\ "De Chelonian Mobile"
> : (_,\/ \_/ \ TortoiseSVN
> : \ \_/_\_/> The coolest Interface to (Sub)Version Control
> : /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-05-31 13:38:12 CEST