forked from bucardo/check_postgres
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.dev
66 lines (48 loc) · 2.06 KB
/
README.dev
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
53
54
55
56
57
58
59
60
61
62
63
64
65
This file is to help developers of the check_postgres program.
Additions are welcome!
** TESTSUITE **
For testing PostgreSQL 9.2 and later, DBD::Pg 2.19.3 is required.
Running the testsuite:
* env -i make test
* LC_ALL=C make test
* initdb and friends not in $PATH: LC_ALL=C make test PGBINDIR=/usr/lib/postgresql/9.2/bin
* Run a single test: LC_ALL=C make test TEST_FILES=t/02_database_size.t
* Skip network tests: LC_ALL=C make test SKIP_NETWORK_TESTS=1
The testsuite is sensitive to locale and PG environment variables such as LANG
and PGDATABASE. Using `env -i` will unset all variables from the user
environment for running the tests.
** RELEASE PROCESS **
Quick notes on the current release process:
* Make sure all changes are recorded in the relevant POD section.
* Add a release date next to the new version number
* Change the version number everywhere (use `RELEASE_TESTING=1 prove -v t/00_release.t` to verify)
* git commit as needed
* Run: perl Makefile.PL; make html
* Run: make signature_asc
* Run: make signature
* Run: git commit -a
* Add a new tag: git tag -u 14964ac8 1.2.3 -m "Version 1.2.3, released August 3, 2009" <commit>
* Run: export TEST_SIGNATURE=1 TEST_CRITIC=1 TEST_SPELL=1 TEST_POD=1 TEST_AUTHOR=1
* Run: make distclean; perl Makefile.PL; make disttest
* git commit as needed
* Run: make dist
* git push
* git push --tags
Login to the bucardo.org box, and then:
* cd code/check_postgres
* git pull
* make distclean; perl Makefile.PL; make disttest; make dist
* prove -v t/00_release.t
* cd ~/www/downloads
* cp -i ~/code/check_postgres/check_postgres* .
* ln -sf <latest tarball> check_postgres.tar.gz
* cd ~/www/check_postgres
* ln -s ../downloads/<latest tarball> .
* edit latest_version.txt
* edit index.html
* Edit the bucardo.org page and bump the version: http://bucardo.org/check_postgres
* Email to check_postgres-announce with summary of changes
* Email the Postgres Weekly News
* Email pgsql-announce if this is a major version
Once the new version is out there:
* Go through and make sure all bugs solved in this release are marked as resolved.