Version 1.2.99 of CAMSEG (1.3 Release Candidate) has been released. This is the first release of CAMSEG 1.3. All the features planned are now done. The next version (final) will only focus on bug fixes. A lot of new features, such as suppliers, taxes and new reports have been added to this new version. For more details, just look at the change log.
To download this version, you need to select “Browse All Packages” from the “Download” menu. There, you select the “CAMSEG 1.2″ release. Please note that it’s still a RC version, so there can be bugs left.Version 1.2 is strongly recommended for a normal usage.
The final release of 1.3 should be available in about 1 week.
All the help and suggestions are welcomed. Feel free to post comments about this release or CAMSEG in general, or write me an email at : lucasr.mal at gmail dot com.
The release schedule of CAMSEG 1.3 has been changed. Due to some ‘mess’ in the back-end, a version 2.0 of CAMSEG with a new, cleaned and improved back-end has been planned. CAMSEG 1.3 is still the next release, but it will contain less features than planned. Also, there won’t be any Beta version, only a RC and a Final. Version 1.3 will still add several new features, such as :
- Support for taxes
- Support for multiple suppliers
- More detailed information about the campaign organization
- Better Invoices and Final Order reports
- Bug fixes
New release schedule :
- libCAMSEG 2.0 Beta 1 C++ Version (1.99.91) : May 6th
- libCAMSEG 2.0 Beta PHP Version (1.99.91) : May 14th
- CAMSEG 1.3 RC (1.2.99) : May 9th
- CAMSEG 1.3 Final : around May 18th
- libCAMSEG 2.0 Beta 2 C++ Version (1.99.92) : TBA (maybe around May 18th ???)
- CAMSEG 2.0 Beta (1.99.91) : TBA (maybe around May 21st ???)
Note that the back-end will not be in the front-end anymore. A separate library (libCAMSEG) will be created, and will be used by the front-end. Also, the Web Interface will now be object oriented, with a PHP separate back-end too. This separation between the back-end and front-end will create a flexible API to use , to ultimately being able to create alternatives front-ends for different usages. Ex: it will be possible to use CWI backend in an existing website, just having to use the methodes of the backend and integrate them into the website, without having to use the default CWI Interface.
