File: Release.Checklist

package info (click to toggle)
libdbd-informix-perl 2003.04-3
  • links: PTS
  • area: contrib
  • in suites: etch, etch-m68k, sarge
  • size: 1,232 kB
  • ctags: 467
  • sloc: perl: 7,349; ansic: 5,340; sh: 184; makefile: 58
file content (52 lines) | stat: -rw-r--r-- 1,988 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
Checklist for Releasing a New Version of DBD::Informix
======================================================

1.  Announce
    - Up to date email addresses
    - Up to date summary of ChangeLog
    - Up to date summary of future directions
2.  Makefile.PL
    - Correct pre-requisite version of Perl
    - Correct pre-requisite version of DBI
    - Correct latest version of DBI
3.  Informix.pm
    - Correct version number
    - Correct pre-requisite version of DBI
4.  ChangeLog
    - All details up to date.
    - Release date annotated.
5.  Notes/Working.Versions
    - Current working versions
6.  README
    - Correct information
    - Correct pre-requisites
    - Correct cross-references
7.  lib/DBD/Informix/TechSupport.pm
    - Up to date email addresses
8.  QA Tests
    - Run some tests specifying username and password via
      DBD_INFORMIX_USERNAME and DBD_INFORMIX_PASSWORD environment
      variables.
    - Run some tests (especially on HP-UX) with
      DBD_INFORMIX_RELOCATABLE_INFORMIXDIR set.
    - Run some tests with no ESQL/C and using "ESQL=c4gl perl Makefile.PL".
      Note that this only works reliably if you're using the same compiler
      that the c4gl script expects to use.  For example, on Solaris 7,
      using Perl built with GCC fails because the '-K PIC' options passed
      by c4gl are not understood by GCC.  You can fix this with the two
	  environment variables:
	  DBD_INFORMIX_ESQLCC_REMOVE_OPTIONS_REGEX
	  DBD_INFORMIX_ESQLLD_REMOVE_OPTIONS_REGEX
    - Ensure that username and password are not always the same to spot
      test failures better.
    - Run regression tests from regression sub-directory.

Note: with an Atria-based CM system, you can probably simplify some of
the versioning stuff.  In fact, we could probably do so with RCS, too.

Much of this is automated by the NewRelease script, but not all of it
can be automated by the NewRelease script.

--

@(#)$Id: Release.Checklist,v 100.5 2002/12/15 00:31:33 jleffler Exp $