Subject: Re: CVS commit: src/distrib/notes/common
To: Pavel Cahyna <pavel@NetBSD.org>
From: Daniel Carosone <dan@geek.com.au>
List: source-changes
Date: 10/01/2007 09:23:56
--raC6veAxrt5nqIoY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sat, Sep 29, 2007 at 12:16:36PM +0000, Pavel Cahyna wrote:
> We would like to have the -current release notes describe netbsd-4,
> so we can synchronize the netbsd-4 notes completely from -current.

As a general observation, this seems very wrong to me.  Documentation
in a branch (incl mainline) should describe the software in that
branch.  We want to encourage/mandate that documentation be updated to
match as the code changes are made, and this means your ability to
make changes in one branch depends on the status of another branch.

> If you have updates which don't apply to netbsd-4 please wait until
> the release...

No criticism implied at all, but this clearly illustrates my point: it
would mean that nobody could have updated release notes for 5.0 in the
past year.

I know what you're trying to do, and the fact that nobody has made
such updates means that the current release notes can, in practice and
"by accident", be synced in bulk as you describe.  I just want to be
clear about not setting this kind of precedent or policy in general.

--
Dan.
--raC6veAxrt5nqIoY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFHADALEAVxvV4N66cRArh/AKDIR4j+6nGwQtQKqiRyEzHEK27XVgCfQUt2
aih8Gujta9EIRY9m0/xaQ0A=
=uH05
-----END PGP SIGNATURE-----

--raC6veAxrt5nqIoY--