Date: Sat, 2 Mar 2002 07:17:34 -0500 From: Michael Lucas <mwlucas@blackhelicopters.org> To: Udo Erdelhoff <ue@nathan.ruhr.de> Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Official -doc freeze proposal Message-ID: <20020302071734.A82120@blackhelicopters.org> In-Reply-To: <20020302112006.Q56195@nathan.ruhr.de>; from ue@nathan.ruhr.de on Sat, Mar 02, 2002 at 11:20:06AM %2B0100 References: <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org> <20020226094226.B55250@blackhelicopters.org> <200203010100.g2110e001512@bmah.dyndns.org> <20020301032142.GA46101@hades.hell.gr> <3C7EF912.30001@pittgoth.com> <20020301090953.A87015@eborcom.com> <20020302112006.Q56195@nathan.ruhr.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 02, 2002 at 11:20:06AM +0100, Udo Erdelhoff wrote: > [trimmed cc: list and subject] > > I have had mixed feelings about the freeze before but this a very > important point. I do remember some rather frustrated mails from > Jordan when problems with the documentation broke the release > building process again and again. > Well, it does help that we have a -doc member who is part of the releng team. If we break it, Bruce will fix it. Lucky Bruce. :-) > So, basically, here's another vote for a 'hard' freeze of the > documentation. I just want to add a vote of caution: Even in > the hard freeze, it should still be possible to fix typos and > similar stuff in the english documentation... Good point. The release engineers allow certain changes during code freeze. Do we want to allow changes during -doc freeze? Here's my opinion: My gut reaction is that a freeze is a freeze, and that we should freeze for anything not blatantly, obviously wrong. We're not really debugging, we're giving translators time to catch up. While I intend to follow this rule, I suspect other -doc people will have other ideas. So, howe about: Changes that do not directly affect the translation teams should be allowed. This basically means typos. We should directly notify the translation teams of these changes. Breaking the -doc build should be a definite no-no during this time, and anything that causes a break or breaks "make release" should be immediately backed out or fixed. How does that sound? (Sorry to be pedantic here: we're seeing what a lack of ground rules is doing to other parts of the Project at the moment. I don't want -doc to have those sorts of issues. Nik is a nice relaxed team lead, and if we can agree on these things ourselves he won't start to hate us all come release time. :-) ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020302071734.A82120>