Re: [Cvs-dev] Re: [Cvs-test-results] CVS trunk testing results (BSDI BSD/OS)

[Jim Hyslop]

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

Derek R. Price wrote:
> Given the sensitive nature of gnupg, do we really want to cater to a
> gnupg that is over 5 years old (it was released 2000-09-20) in the
> test suite?  I'm inclined to say no.

I agree.

> Perhaps a target that only runs with
> --enable-maintainer-mode (better yet, as part of a maintainercheck or
> the distcheck target) that polls gnupg.org for the latest release and
> warns if the "latest gpg" version number is out of date?  Am I going
> overboard?

Depends on your perspective :=) From the security point of view, not in
the least. Some paranoi^H^H^H^H^H^H^H conscientious security people
might say you aren't going far enough.

I think we should not test for a specific revision of GPG. Keeping GPG
up to date is outside the scope of CVS. We should take every reasonable
effort to ensure that CVS works properly with the latest version of GPG,
and to that extent we should ensure that sanity.sh tests pass properly.

It would probably be helpful to have a reminder for the maintainers to
make sure it's up to date, and possibly allow the reminder to be
user-configurable for those users who may want to be reminded as well.

- --
Jim Hyslop
Dreampossible: Better software. Simply.     http://www.dreampossible.ca
                 Consulting * Mentoring * Training in
    C/C++ * OOD * SW Development & Practices * Version Management

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEX3z7LdDyDwyJw+MRAsIBAKCWQWrRRtJecZgEx6k7YFq1byIvTgCg7Xnk
l/vtADydRb7+Hx85glNtCdw=
=rRm7
-----END PGP SIGNATURE-----