Date: Mon, 28 Jan 2013 13:52:02 +0100 From: Gabor Kovesdan <gabor@FreeBSD.org> To: Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> Cc: doc@freebsd.org Subject: Re: RFC: Dealing with version-specific docs Message-ID: <51067472.5000902@FreeBSD.org> In-Reply-To: <CAOgwaMuhHgA2bEBFExnS9poOg84qXDK810x60Fh47O6EiW0fXg@mail.gmail.com> References: <51065CFC.5090803@FreeBSD.org> <CAOgwaMuhHgA2bEBFExnS9poOg84qXDK810x60Fh47O6EiW0fXg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Em 28-01-2013 13:15, Mehmet Erol Sanliturk escreveu: > I think , the required effort for version specific Handbook is much > less than multiple version covering Handbook , because , if any change > is not applied to a prior version , which is mostly the case , > its Handbook will also not be modified . > If a change is applied to a version and it is copied also to prior > versions , the changes to the Handbook may also be copied to their > Handbooks . This will not be difficult than to modify a multiple > version contained Handbook . > > As a result , again my primary suggestion is to make the Handbook > version specific : When a version is branched , its Handbook and > related other documentation also should be branched and maintained > with the related version . Mehmet, thanks for the comments but I was interested in comments of that very specific technical solution that I proposed on the linked wiki page. The necessity of handling version-specific information has been discussed several times both on the lists and on conferences so please let's focus on technical solutions rather than going back to general discussions. If you see the linked page, there was no branching mentioned there, it is a much easier and simpler approach. Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51067472.5000902>