0.7.5 (was: BerkeleyDB woes on FreeBSD)

[Matthias Andree]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 07 Oct 2002, Adrian Otto wrote:

> Probably the best way to deal with this for our 0.7.5 release is to make a
> README.FreeBSD file that explains how to invoke the configure script to get
> a successful build with db4.

I plan to make a FreeBSD port instead, because manual installation of
software is discouraged on FreeBSD: it bypasses the packaging system.
This port should be able to deal with that. I'd only like to see
- --with-db-header and --with-db-includes, but I don't have time for that
right now, and it can wait until after 0.7.5.

One thing I'd like to suggest is: as soon as we are in for serious 0.7.5
release steps, please branch. Let's do "cvs update", then "cvs tag -b
branch-0-7-5" and tell us to use that branch  (cvs update -r
branch-0-7-5), and as the final release happens, please tag it as well,
on the 0.7.5 branch: "cvs tag release-0-7-5". That way, we have quick
means to access older releases in the future, to figure what has
changed, and to fix important bugs in a release when the next real
release is some time away.

If someone is going back to the HEAD branch, then cvs update -A will do
the job.

That way we have a "stable" release branch we only fix bugs in but can
still commit new features to the "new" branch without affecting 0.7.5.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9oscpFmbjPHp/pcMRAjgSAKCDrvz9uTueS5fNXoZ7DrwaLv7aZACdHkea
j+6qAOwosd+sbtTChc46Quk=
=m1eI
-----END PGP SIGNATURE-----