[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

SF.net SVN: ledger-smb:[3940] branches/1.3



Revision: 3940
          http://ledger-smb.svn.sourceforge.net/ledger-smb/?rev=3940&view=rev
Author:   einhverfr
Date:     2011-10-28 23:09:00 +0000 (Fri, 28 Oct 2011)
Log Message:
-----------
Changes for 1.3.3

Modified Paths:
--------------
    branches/1.3/Changelog
    branches/1.3/LedgerSMB/Form.pm
    branches/1.3/LedgerSMB.pm
    branches/1.3/UPGRADE
    branches/1.3/VERSION
    branches/1.3/dists/rpm/ledgersmb.spec
    branches/1.3/dists/source/build.sh
    branches/1.3/doc/release_notes

Modified: branches/1.3/Changelog
===================================================================
--- branches/1.3/Changelog	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/Changelog	2011-10-28 23:09:00 UTC (rev 3940)
@@ -10,8 +10,12 @@
 * API inconsistency fixed (Chris T)
 * Fix for translation string standardization (Herman V)
 * Fix for AP posting issue with 1.000,00 number format (Herman V)
+* More number format fixes (Herman V)
 * Database upgrade within 1.3 now possible from setup.pl (Chris T)
 
+Chris T is Chris Travers
+Herman V is Herman Vierendeels
+
 Changelog for LedgerSMB 1.3.2
 * Fixed a few files where suExec fixes were not applied (Chris T)
 * Fixed erroneous buttons marked "Save and Post" showing up (Chris T)

Modified: branches/1.3/LedgerSMB/Form.pm
===================================================================
--- branches/1.3/LedgerSMB/Form.pm	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/LedgerSMB/Form.pm	2011-10-28 23:09:00 UTC (rev 3940)
@@ -150,7 +150,7 @@
     #menubar will be deprecated, replaced with below
     $self->{lynx} = 1 if ( ( defined $self->{path} ) && ( $self->{path} =~ /lynx/i ) );
 
-    $self->{version}   = "1.3.2";
+    $self->{version}   = "1.3.3";
     $self->{dbversion} = "1.3.3";
 
     bless $self, $type;

Modified: branches/1.3/LedgerSMB.pm
===================================================================
--- branches/1.3/LedgerSMB.pm	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/LedgerSMB.pm	2011-10-28 23:09:00 UTC (rev 3940)
@@ -220,7 +220,7 @@
 $CGI::Simple::POST_MAX = -1;
 
 package LedgerSMB;
-our $VERSION = '1.3.2';
+our $VERSION = '1.3.3';
 
 my $logger = Log::Log4perl->get_logger('LedgerSMB');
 

Modified: branches/1.3/UPGRADE
===================================================================
--- branches/1.3/UPGRADE	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/UPGRADE	2011-10-28 23:09:00 UTC (rev 3940)
@@ -1,93 +1,41 @@
-Upgrading to LedgerSMB 1.2 
+Upgrading to LedgerSMB 1.3.3 
 
-From LedgerSMB (1.1.1 or earlier) 
-or 
-SQL-Ledger (2.6.19 or earlier)
+From LedgerSMB 1.3.0-1.3.2:
 
-This document contains information on how to upgrade from earlier versions of 
-LedgerSMB or SQL-Ledger.  This upgrade is a major revision and may not go 
-smoothly.  We recommend that the reader start by reading the section on manual
-installation and then start by trying the automated means mentioned later.
+Untar over the top and then:
 
-Also this document assumes that the reader is already familiar with the release
-notes.  If you have not already done so, please read the release_notes file in
-the doc/ directory.
+1)  Shell script process (UNIX/Linux only):
 
-Before you begin, make sure that you are running at least PostgreSQL 8.0.  If 
-you are running a prior version, you will need to dump your data, upgrade the 
-database server and restore the data before proceeding.
+* cd to the sql/modules directory of the ledgersmb installation.
+* sh reload_modules.sh [dbname] 
+* repeat the shell script for each database for each database
 
-MANUAL UPGRADE:
-===============================================================================
+2)  Automated process (all platforms):
 
-1)  Back up old installation
-THis is a major upgrade.  If something goes wrong, you want to be able to get
-back to a known good state.  To back up the old installation do as follows:
-  a)  Copy the LedgerSMB install directory (for example /usr/local/ledger-smb) 
-      to another location
-  b)  Back up the database using pg_dump or other PostgreSQL backup program.
-  c)  (optional) Make a live bakup of the accounting database by creating a new
-      db with it as the template.  Something like:
-      createdb -U postgres -T ledgersmb accounting_backup
+* direct browser to the setup.pl file in the directory you are in.
+* provide PostgreSQL superuser credentials and the name of your data base.
+* Click continue.
+* Repeat for each database.
 
+From LedgerSMB 1.1 and earlier:
 
-2)  Check New Dependencies
+For versions prior to 1.2, please upgrade to LedgerSMB 1.2 before upgrading to 
+1.3.x.  To do this upgrade, simply untar the version of 1.2.x over your old
+installation and run the relevant database upgrade scripts (in
+sql/upgrade/legacy).  Then proceed below.
 
-The Build.PL script can be used to test for unmet dependencies and run other
-tests.  It doesn't install anything yet, but it will tell you what you are 
-missing.  To check for dependencies, run "perl Build.PL" from the command line.
-Missing dependencies can generally be installed via a Linux distributor's
-package manager or by CPAN.
+From LedgerSMB 1.2.x
 
-Once this is done and dependencies are satisfied, you can check to see whether
-the installation nominally works by running "./Build test" from the command
-line.  The test suites currently check to make sure all the perl modules load
-and that a number of numeric tests are passed.
-
-Dependencies which are recommended are needed only for specific functionality
-and may not be required in all circumstances.  These include:
-  * Net::TCLink for credit card processing in a POS environment
-  * Parse::RecDescent for the CLI script host
-
-3)  Upgrade database
-
-  a) cd to the sql/legacy/ directory of the new ledger directory
-  b) run "psql" with appropriate options to connect to your database.
-  c) Note the db schema version by running the following query:
-     "SELECT value from defaults where setting_key = 'version';" (1.2.0 or 
-     later)
-       or
-     "SELECT version FROM defaults;" (SQL-Ledger 2.6.x or LedgerSMB 1.1.x 
-     or earlier)
-  d) Run the SQL upgrade scripts in order starting with the one whose name
-     begins with "Pg-upgrade-[version]" (each of these scripts will upgrade to
-     the next database version which is also identified in the file name).
-
-Note that this will create three tables that may not actually be used depending
-on your setup:  users, users_conf, and session.  In general if you have multiple
-datasets, these tables will only be used in one.
-
-4)  Decide where to put the user/session management tables.  In general, we
-recommend as follows:
-  a)  Single dataset installations should use the user tables in the dataset.
-  b)  Multicompany installations should use user tables in a separate dataset
-      from any accounting data.
-
-If you need to create another dataset, you can create the db and import the
-sql/Pg-central.sql file into it.
-
-5)  Set the admin password:
-  a)  From psql, determine what admin password you wish to use.  Then type:
-      "update users_conf set password = md5('my_password');"
-      Naturally you would use your password instead of my_password.
-
-6)  Import the users.  Run the import-members script to do this.
-
-7)  Copy the files from the LedgerSMB tarball over your existing installation.
-8)  Delete the users directory.
-
-9)  Edit the ledger-smb.conf file as appropriate.
-
-Congratulations, you have manually upgraded to LedgerSMB 1.2.
-
-TODO:  Add upgrade.pl script and automate the above process.
+* Untar over the top.
+* Check your Perl dependencies:
+   * perl Makefile.PL
+   * make
+   * make test
+* run the install.sh script.
+* direct your browser to the setup.pl script in your ledgersmb directory (via
+  http) and follow the prompts:
+   * Provide Pg superuser and database information for your existing database
+   * Click continue when asked to upgrade
+   * Provide user information.
+   * log into the application and create additional users under System/User
+     Management

Modified: branches/1.3/VERSION
===================================================================
--- branches/1.3/VERSION	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/VERSION	2011-10-28 23:09:00 UTC (rev 3940)
@@ -1 +1 @@
-1.3.2
+1.3.3

Modified: branches/1.3/dists/rpm/ledgersmb.spec
===================================================================
--- branches/1.3/dists/rpm/ledgersmb.spec	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/dists/rpm/ledgersmb.spec	2011-10-28 23:09:00 UTC (rev 3940)
@@ -1,7 +1,7 @@
 # RPM spec written for and tested on CentOS 4 and CentOS 5 
 Summary: LedgerSMB - Open Source accounting software
 Name: ledgersmb
-Version: 1.3.0
+Version: 1.3.3
 Release: 1
 License: GPL
 URL: http://www.ledgersmb.org/

Modified: branches/1.3/dists/source/build.sh
===================================================================
--- branches/1.3/dists/source/build.sh	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/dists/source/build.sh	2011-10-28 23:09:00 UTC (rev 3940)
@@ -2,7 +2,7 @@
 
 # Simple script to prepare for release
 
-version="1.3.2";
+version="1.3.3";
 build_d="../release";
 
 if test -d $build_d/ledgersmb; then

Modified: branches/1.3/doc/release_notes
===================================================================
--- branches/1.3/doc/release_notes	2011-10-28 10:19:17 UTC (rev 3939)
+++ branches/1.3/doc/release_notes	2011-10-28 23:09:00 UTC (rev 3940)
@@ -1,8 +1,8 @@
 RELEASE NOTES
 LedgerSMB 1.3
 
+Latest Revision:  1.3.3, October 28th.
 
-
 1:  Welcome to LedgerSMB
 
 LedgerSMB is an accounting and ERP program initially aimed at small to midsize
@@ -15,7 +15,7 @@
 
 * Perl 5.8.
 * Apache, IIS, or other web server that supports CGI.
-* PostgreSQL 8.1 or higher.
+* PostgreSQL 8.2 or higher.
 * Any operating system that supports the above environment.
 * The following CPAN modules:
 	* Data::Dumper

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.