Date: Thu, 2 Sep 2010 19:54:39 -0300 From: Daniel Gerzo <danger@rulez.sk> To: Ed Schouten <ed@80386.nl> Cc: "doc@freebsd.org" <doc@freebsd.org>, "current@freebsd.org" <current@freebsd.org> Subject: Re: Call for Documentation Contributors Message-ID: <45764F17-2279-4520-93D7-8F0B8BE991DE@rulez.sk> In-Reply-To: <20100902080219.GH64651@hoeg.nl> References: <AANLkTim=VBiPgEpo=j6BVxHRB2on%2BcaJaGHsUwzGoBao@mail.gmail.com> <AANLkTinVhbb3aK%2BKCEe_4Y7kx00844HW7pktmJwPnR%2Bj@mail.gmail.com> <20100902080219.GH64651@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
I actually think there is some point in this idea. The problem is that many times we just leave notes or warnings specific for given releases, which can many times lead to confusion (or people just don't notice) and as time goes and we cut the support for given releases they get stale (e.g. We had many of those for 5.x). We could just maintain the handbook in separate branches like we do with src, keeping them all built online, and merge relevant things where appropriate. This will, however, add quite a lot (for my taste) of additional work for us. Daniel Gerzo On 2.9.2010, at 5:02, Ed Schouten <ed@80386.nl> wrote: > * Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> wrote: >> Please separate Handbook with respect to distributions , i.e. , maintain a >> different Handbook for each distribution . > > The problem with that is that it will cause documentation for older, but > still supported releases, to become stale. Most doc changes apply to > functionality provided by both releases, or at least functionality that > is MFC'd. > > -- > Ed Schouten <ed@80386.nl> > WWW: http://80386.nl/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45764F17-2279-4520-93D7-8F0B8BE991DE>