ZAP - Improve our release practices


Subject: ZAP - Improve our release practices
From: sam th (sam@bur-jud-118-039.rh.uchicago.edu)
Date: Tue Jan 18 2000 - 04:32:29 CST


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

I went through ESR's page on appropriate release practices and came up
with the following TODO's (broken down by category)

        Code changes
1 portability
        we obviously want to use an extremly portable subset of ANSI C++.
        to that end, we need to fix bug 238, relating to non-standard
        string fuctions
2 location of BUILD.TXT
        ESR thinks it should be in abi, and not in abi/docs. I agree,
        however, this should be discussed

        Non-code changes
1 website
        ESR thinks we should have more documentation on the site, and
        frankly, i agree with him. at a minimum, the contents of abi/docs should
        be availible online. someone should also start work on a manual,
        but that's another story
2 filenames
        ESR dislikes the underscore. he belives that *_static_* should be
        changed to *.static.* for example. i think this is sort of minor, but it
        could be discussed
3 ftp sites
        this is important. metalab, the most important linux ftp site,
        has shockingly old versions of abiword. this should be fixed ASAP, along
        with other ftp sites. (rpmfind, etc)

        other changes
autoconf, automake, etc vs diving make
this is for far in the future

           
                                     sam th
                                     sytobinh@uchicago.edu
                                        
ps
        i skipped the reccomendation to use C.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4hEE/t+kM0Mq9M/wRAid3AKCpzqqyJ5+PQvp7l/S6bkuqIdVPIgCfc6ST
M5GhGn7u0R13H9CGRZRq90w=
=fXRJ
-----END PGP SIGNATURE-----



This archive was generated by hypermail 2b25 : Tue Jan 18 2000 - 04:32:32 CST