--sA0T44BA86podSFD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Oct 15, 2005 at 02:48:02PM +0200, Remko Lodder wrote:
> Marc Fonvieille wrote:
> >On Sat, Oct 15, 2005 at 01:20:37PM +0100, Ceri Davies wrote:
> >
> >>[ Moved to doc@ from some other place ]
> >>
> >>On Sat, Oct 15, 2005 at 05:58:37AM -0400, Tom Rhodes wrote:
> >>
> >>
> >>> Or perhaps
> >>>4.X will be knifed from the handbook. And most likely, the
> >>>only people who will expect it coming will be those that aren't
> >>>going to stand in my way.[1] :)
> >>>
> >>>[1]: Please don't take that as if it's rude, I'm actually
> >>> joking around with it. Cause I know that if someone
> >>> tried that, well, to core && doceng they'd be explaining.
> >>
> >>Actually that's a great idea. There's no reason why we couldn't, like
> >>today, commit a copy of the current handbook to handbook4 and then get
> >>rid of all the crud from the real handbook. Same deal with the FAQ.
> >>The information is still available then, but we no longer have to tear
> >>our own hair own trying to maintain the documents.
> >>
> >
> >
> >If people agree with that idea, let's freeze a Handbook4 and stop
> >"supporting" 4.X in docs. (By "freeze" I mean no any new
> >addition/change beside typos.) Let's then create a HANDBOOK_4 (or
> >something like that) tag for CVSup operations.
> >We could do the same for Handbook5 when 5.X will be dropped.
> >Well, we could do the same as the Security Officer and set up a schedule
> >for releases Handbook/docs support; this schedule will allow us to know
> >when a HandbookX freeze will happen.
> >
> >Marc
>=20
> I am very much in favor of this idea. Though, should we really tag=20
> another branch? We recently branched the documentation for RELENG6
> so we might want to just use that? instead of duplicating that
> information. On the other hand, a nice schedule and the availability
> of 'old' unused branches is also very nice.
I guess that this really would count as "sweeping", which means that
we'll have to wait a week or two. At least that allows us plenty of
time to finalise the plans.
The important points are:
i) Handbook-4 must still be available on the website, probably
via the URL /doc/<lang>/handbook4/;
ii) We must be able to rip out all the [1-4].x information that
is in our way from the current handbook.
To me, that means:
i) Laying down a (PRE_)HANDBOOK4 CVS tag;
ii) Repocopying doc/<lang>/books/handbook to
doc/<lang>/books/handbook4 for each language;
iii) Perhaps throwing the build of that directory under a
(defaulted to off) knob (that the web build can turn on).
where bits in parentheses may or may not make sense.
There's no reason not to lay down a new tag, especially now. If this
becomes part of the release cycle proper then we could omit it then, but
it's too late now for 6.
Ceri
--=20
Only two things are infinite, the universe and human stupidity, and I'm
not sure about the former. -- Einstein (attrib.)
--sA0T44BA86podSFD
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
iD8DBQFDUP34ocfcwTS3JF8RAuPBAKDHhxR7O64iDcaYfu4OJQpCcdQhSQCghyfK
xmpARnTNnUHlSkby7MGgeDk=
=jIOI
-----END PGP SIGNATURE-----
--sA0T44BA86podSFD--