Permalink
Browse files

bump version 3.2.0

add some UPGRADING documentation
  • Loading branch information...
Paul J Stevens
Paul J Stevens committed Aug 23, 2014
1 parent 861bb5e commit 9e196b2be7b4904e5bc63b41cb8c2fec2605ba5f
Showing with 2,032 additions and 3,636 deletions.
  1. +228 −381 Makefile.in
  2. +26 −0 UPGRADING
  3. +349 −562 aclocal.m4
  4. +303 −476 configure
  5. +1 −1 configure.ac
  6. +200 −297 man/Makefile.in
  7. +400 −584 src/Makefile.in
  8. +160 −312 src/modules/Makefile.in
  9. +75 −180 systemd/Makefile.in
  10. +290 −843 test/Makefile.in
View

Large diffs are not rendered by default.

Oops, something went wrong.
View
@@ -1,6 +1,29 @@
Upgrading from DBMail 3.0 to DBMail 3.2
=======================================
Dependencies
------------
* Database: MySQL 5.0 or better, PostgreSQL 8.3+, Sqlite3, Oracle
* Glib: (>= 2.16.0)
* GMime: (>= 2.6.20)
* OpenSSL
* libmhash
* libzdb
* libevent: (>= 2.0.21)
Schema Changes
--------------
* As of dbmail-3.2 auto-migrations are supported, so no manual migrations
are required.
Upgrading from DBMail 2.2 to DBMail 3.0
=======================================
Dependencies
------------
* Database: MySQL 5.0, PostgreSQL 8.3+, or SQLite3
* Glib: (>= 2.16.0)
@@ -13,6 +36,7 @@ Dependencies
* libevent
Config Changes
--------------
* MySQL: notice!
@@ -75,6 +99,7 @@ FILE_LOGGING_LEVELS = 7
SYSLOG_LOGGING_LEVELS = 31
Schema Changes
--------------
Migration scripts from the previous stable releases are provided in
sql/mysql, sql/postgresql and sql/sqlite. Please test them first
@@ -93,6 +118,7 @@ will have to be dropped, re-created, and re-filled using:
dbmail-util -by
Server Changes
--------------
Dbmail until 2.2 used a pre-forking server design with a dedicated
connection to the database backend for each forked process. Even with
Oops, something went wrong.

0 comments on commit 9e196b2

Please sign in to comment.