[368 total ]
Openbravo ERP: 2.50alpha-r11 available

Openbravo ERP is a Web based ERP for SME, built on proven MVC & MDD framework that facilitate its customization. Already in production, Openbravo ERP encompasses a broad range of functionalities such as finance, supply chain, manufacturing & ... [More] much more.

Featuring an exciting new modular architecture, usability improvements and broader functional coverage, Openbravo ERP 2.50 is the latest release of the leading open source ERP solution. This is an alpha version and it is intended for evaluation and stabilization purposes only. Openbravo 2.40 remains our best version for production usage. You cannot upgrade an existing system to 2.50alpha-r11 and you will not be able to upgrade a 2.50alpha-r11 instance to any subsequent version.

-- What is new --

For a list of feature included in this release, check the release notes:

http://wiki.openbravo.com/wiki/Openbravo_ERP_2.50_ReleaseNotes#New_Features

-- Test it --

We do encourage you to download and test this new version and give us your feedback. You can post your opinion and question on the new features in the Early Releases Discussion forum (http://sourceforge.net/forum/forum.php?forum_id=808030) and you can log any defect that you might find in the product using our issue tracking system (http://issues.openbravo.com).

In this release, you can install Openbravo ERP following two different approaches:

* Community Appliance (recommended): you can download and install a fully configured appliance that runs in your preferred virtualization environment. The appliance includes both Openbravo ERP as well as its underlaying technology stack and allows you to get started with Openbravo in just a few minutes and with only a few clicks. The images are available for the VMware, VirtualBox, QEMU, Parallels and Xen virtualization systems. To download these images:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783

* Custom installation (experts only): a custom installation gives you full control over your deployment environment and allows you to choose your preferred configuration for the technology stack. However, it requires you to install and configure all components of the technology stack as well as compiling Openbravo ERP from sources. You can to obtain a copy of the source code by either:

- Downloading a source code tarball:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783&release_id=660827

- Checking out the source code from the Openbravo Subversion repository

https://dev.openbravo.com/svn/openbravo/tags/r2.50alpha-r11/

Download and test it following our installation and configuration guide:

http://wiki.openbravo.com/wiki/Openbravo_ERP_Installation_2.50 (0 comments) [Less]

Rob Goris: Concepts for Openbravo ERP Redesign

We are continuously improving our products and raise the bar with every release. Recently we have started to look at some very fundamental parts of the User Interface of Openbravo ERP and came up with ideas for a future redesign. User feedback told ... [More] us that there is a need for more powerful and flexible search functionality. We also learned that many user like to edit the grids (tables) directly in the cells and that switching between different records at the same time would be very useful. Furthermore, we are looking at offering more functionality in the context of tasks and we also believe that there is a need for more high level and summarized views on data.

Here we would like to give you a peek preview of the stuff we are working on and give you the opportunity to give your feedback. Our approach is holistic: we believe that all functionality should be working in the context of user journeys rather than just plugging in new features left and right. That's why we also want to propose a complete new Master-Detail concept in which all other functionality is embedded.

Images say more than words so check out the Demo Videos and discuss them on the User Experience Lab forum:

Please also fill out the surveys for Master Detail, Search & Filter, My Workspace and Overall Impression.

I am looking forward to a lively discussion.

Thanks, Rob [Less]

Asier Lostalé: New build process: keep it simple

(Old) Problems
For Openbravo ERP developers (specially for newcomers) it has always been difficult to decide which of the available build tasks was the best election to build the system after any development they had done. We had to take into ... [More] account what modifications were done to know which ant task we should run. For example if we had modified a window we would use ant compile -Dtab=myWindow to generate the code just for that window and not for the rest of them.  It was even worse when working with subversion, each time we updated our working copy we had to look which were the files that had been updated to know if it was necessary to run update.database to synchronize Openbravo model database(database schema objects and applicatoin dictionary data) from XML files. And in case there were modifications there it was worth re-generate all the WAD windows because it was difficult to know which ones had been modified. So many times compile.complete was the “safe” but slow choice.

Upadate.database task had two more inconvenients: the first one was that in case Openbravo model was modified locally and not exported (ant export.database), when executing this task we would lose all the changes done in database for application dictionary. This annoying behavior had been reported as a bug. The other inconvenient was that during the r2.50 development cycle, specially because of the usage of DAL as part of the update process, this task was pretty unstable, making people not to be very confident about using it. As result people felt safer by recreating the whole system  (ant install.source) instead of executing a much faster incremental build (ant update.database compile.complete).

New task: smartbuild
For Openbravo ERP r2.50 we have resolved these problems by simplifying the build process with a new incremental build task: smartbuild, which is currently available in trunk (r12753) and will be release in the next alpha (aplha r11). This task performs all the required processes to build your  system but only the required ones, with a huge improvement in performance. It checks whether the database needs to be updated from xml sources and performs the update only if needed, generates the code that needs to be regenerated, compiles and deploys it.

The goal of this smartbuild is to replace most of the rest of tasks, making life a little simpler for developers. So now it is only needed to use two tasks: smartbuild for all the builds and export.database to export database to xml files. export.database is now smart to export only if needed, skipping the process if no changes have happened in the local Openbravo model.

Moreover update.database ensures before updating that no local changes have occured in Openbravo model since the last synchronization (export.database or update.database) to prevent people loosing their changes. In case of changes, people will be required to export their database before updating it.

How it works

Determine if database needs to be updated. To do this smartbuild generates a checksum for the xml files and compares it with an existent one. This one is generated each time database is synchronized from xml files or to xml files. If the two checksums are different it means that xml files are different so database is updated.
Decide which code needs to be re-generated. Whenever a build process is done a timestamp with the current time is stored in database. This timestamp is compared with the audit info for the application dictionary objects that participate in the code generation so now WAD is able to generate code only for those elements that have been created or modified after the last build. Additionally when exporting database to xml files the audit info is not longer exported and when updating the audit info is recalculated for the current time, thus it also works in case the modifications in application dictionary came from an update.database. There’s only one case when this check doesn’t work: it is when application dictionary elements are modified directly in databse through insert/update SQL statements without updating audit info. In this case the developer will have to generate the code in the old way (using compile -Dtab=modifiedWindows).
Check if database has been changed. This check allows to export only if there’re changes in database and prevents data loses when updating database. To check this it is used the same timestamp as in the first point. Modifications in data are calculeted by DAL and modifications in database structure are queried directly to database. The query for database structure last modification has no problem in Oracle becuase User_Objects table stores the last physical change for each database object, but in PostgreSQL that information is not stored in database. This has been solved for PostgreSQL generating a checksum in database from all the elements in database that can be exported to xml files, that’s the reason why in PostgreSQL this check takes longer than in Oracle.

Posted in Openbravo   Tagged: developers utilities, r2.50    [Less]

Openbravo ERP: 2.50alpha-r10 available

Openbravo ERP is a Web based ERP for SME, built on proven MVC & MDD framework that facilitate its customization. Already in production, Openbravo ERP encompasses a broad range of functionalities such as finance, supply chain, manufacturing & ... [More] much more

Featuring an exciting new modular architecture, usability improvements and broader functional coverage, Openbravo ERP 2.50 is the latest release of the leading open source ERP solution. This is an alpha version and it is intended for evaluation and stabilization purposes only. Openbravo 2.40 remains our best version for production usage. You cannot upgrade an existing system to 2.50alpha-r10 and you will not be able to upgrade a 2.50alpha-r10 instance to any subsequent version.

-- What is new --

For a list of feature included in this release, check the release notes:

http://wiki.openbravo.com/wiki/Openbravo_ERP_2.50_ReleaseNotes#New_Features

-- Test it --

We do encourage you to download and test this new version and give us your feedback. You can post your opinion and question on the new features in the Early Releases Discussion forum (http://sourceforge.net/forum/forum.php?forum_id=808030) and you can log any defect that you might find in the product using our issue tracking system (http://issues.openbravo.com).

In this release, you can install Openbravo ERP following two different approaches:

* Community Appliance (recommended): you can download and install a fully configured appliance that runs in your preferred virtualization environment. The appliance includes both Openbravo ERP as well as its underlaying technology stack and allows you to get started with Openbravo in just a few minutes and with only a few clicks. The images are available for the VMware, VirtualBox, QEMU, Parallels and Xen virtualization systems. To download these images:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783

* Custom installation (experts only): a custom installation gives you full control over your deployment environment and allows you to choose your preferred configuration for the technology stack. However, it requires you to install and configure all components of the technology stack as well as compiling Openbravo ERP from sources. You can to obtain a copy of the source code by either:

- Downloading a source code tarball:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783&release_id=658992

- Checking out the source code from the Openbravo Subversion repository

https://dev.openbravo.com/svn/openbravo/tags/r2.50alpha-r10/

Download and test it following our installation and configuration guide:

http://wiki.openbravo.com/wiki/Openbravo_ERP_Installation_2.50 (0 comments) [Less]

Openbravo ERP: 2.50alpha-r10 available

Openbravo ERP is a Web based ERP for SME, built on proven MVC & MDD framework that facilitate its customization. Already in production, Openbravo ERP encompasses a broad range of functionalities such as finance, supply chain, manufacturing & ... [More] much more

Featuring an exciting new modular architecture, usability improvements and broader functional coverage, Openbravo ERP 2.50 is the latest release of the leading open source ERP solution. This is an alpha version and it is intended for evaluation and stabilization purposes only. Openbravo 2.40 remains our best version for production usage. You cannot upgrade an existing system to 2.50alpha-r10 and you will not be able to upgrade a 2.50alpha-r10 instance to any subsequent version.

-- What is new --

For a list of feature included in this release, check the release notes:

http://wiki.openbravo.com/wiki/Openbravo_ERP_2.50_ReleaseNotes#New_Features

-- Test it --

We do encourage you to download and test this new version and give us your feedback. You can post your opinion and question on the new features in the Early Releases Discussion forum (http://sourceforge.net/forum/forum.php?forum_id=808030) and you can log any defect that you might find in the product using our issue tracking system (http://issues.openbravo.com).

In this release, you can install Openbravo ERP following two different approaches:

* Community Appliance (recommended): you can download and install a fully configured appliance that runs in your preferred virtualization environment. The appliance includes both Openbravo ERP as well as its underlaying technology stack and allows you to get started with Openbravo in just a few minutes and with only a few clicks. The images are available for the VMware, VirtualBox, QEMU, Parallels and Xen virtualization systems. To download these images:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783

* Custom installation (experts only): a custom installation gives you full control over your deployment environment and allows you to choose your preferred configuration for the technology stack. However, it requires you to install and configure all components of the technology stack as well as compiling Openbravo ERP from sources. You can to obtain a copy of the source code by either:

- Downloading a source code tarball:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783&release_id=658992

- Checking out the source code from the Openbravo Subversion repository

https://dev.openbravo.com/svn/openbravo/tags/r2.50alpha-r10/

Download and test it following our installation and configuration guide:

http://wiki.openbravo.com/wiki/Openbravo_ERP_Installation_2.50 (0 comments) [Less]

Openbravo's SourceForge news: Openbravo ERP: 2.50alpha-r10 available

Openbravo ERP is a Web based ERP for SME, built on proven MVC & MDD framework that facilitate its customization. Already in production, Openbravo ERP encompasses a broad range of functionalities such as finance, supply chain, manufacturing & much more (0 comments)

Adrián Romero: Openbravo POS 2.30 delayed

As published in the Openbravo POS roadmap, the planned dates for Openbravo POS 2.30 were 30th January 2009 for the beta release and 27th February 2009 for the production release. Unfortunately we have not been able to publish the beta release the ... [More] 30th January and for sure it will not be possible to release the production release on time.

The progress of the development of the features for the 2.30 is going as expected but the development team is not very big and we have accumulated a few weeks of delay due to competing priorities.

If you cannot wait until the release of the beta or the production release because you want to see the progress about features like the PDA module for restaurants, the data integration processes between Openbravo ERP and Openbravo POS, ... You can access the subversion repository, download the sources and compile yourself Openbravo POS. It is very easy and everything is documented. Just follow the steps of the Developer's Guide.

We expect not to delay the publication of the beta and the production releases more than one month. And any change in this situation will be communicated to the Openbravo POS community. Stay tuned... [Less]

Paolo Juvara: 2.50 status update and statistics

It has been 2 months since we launched 2.50 alpha and I would like to give you an update on our progress in the stabilization process.

In short, it is taking longer than we expected and we still are finding many issues. As you might know ... [More] from our wiki, our criteria for completing the alpha testing and starting beta is to reach zero critical and major defects, and less than 100 minor and trivial defects combined.

During 2.40, this process took us 8 weeks so we were expecting that it would have taken roughly the same amount of time for 2.50, but things are not going in the same way.

We started the 2.40 alpha cycle on May 23, 2008 with an overall backlog of 278 open defects. In the 8 weeks till July 18th, when we published beta, 357 new defects were logged and we closed a total of 534, leaving the backlog level at 95 open defects, in line with our exit criteria. The historical trend is summarized in the image below.

When we started 2.50 alpha on the November 21st, we had a similar backlog of 271 product defects. However, since then and up to the end of January 2009, 646 defects have been reported and we have closed 684 defects, leaving the current backlog at 233.
The 2.50 historical trend is in the image below and as you can see, 10 weeks into the alpha cycle, the progress is very uncertain and we have been blocked at this level for a while.

How do we justify that? Have we been sleeping on the job? Actually, we made a lot of progress:
We fixed almost precisely the same number of defects per week in 2.50 as we did in 2.40 (68.4 defects per week in 2.50 vs. 66.7 defects per week in 2.40);We published 9 alpha versions, both in source code format and in the handy appliance format to ease testingWe manned the Modularity Program that supports about 20 early adopters that are actively developing extensions on top of 2.50.
The thing is... the defect inflow has been 40% higher in 2.50 than in 2.40 (65 defects per week vs 45 defects per week) and this is what is slowing us down.

But then... how do we explain this increase? I really do not have a very strong argument to explain it in definitive terms, but I can put forward some theories:
We do a much better job at testing compared to previous releases. In particular, compared to 2.40, our dedicated QA team has grown more than 300%Our community usage of previous releases has grown dramatically in recent months and many users are stressing the systems in ways it was not stressed before. Of the 646 reported defects, 155 (or 24%) have been reported against a production release.
Our community is testing this early release very actively: 2.50 alpha gets downloaded around 800 times a week (without even counting people who install from sources using our SVN repository) and around 10% of the defects are reported by community testers.
The complete explanation is probably a mix of all the above points. Overall, this means that 2.50 is going to be the best release ever in terms of quality. Our exit criteria, in fact, is not time driven but quality driven and we will not release the beta version until the intended level of quality has been reached.

Because we do not have a time boundary, it is difficult for us to predict the availability date of 2.50 beta. We hope that it is going to be within a few weeks but you can monitor the progress of our stabilization effort live: if you are an iGoogle user, click here to add a Google Gadget with daily update of our progress graph as in the image below.

You can help us in this process by contributing to the testing effort. Please do download our latest alpha release and test it out. You can participate in the Community testing program organized by our QA team provided or just verify whatever feature is most important to you. In any case, please do not forget to report your defects! [Less]

Jordi Mas: Single Sign on launched for Openbravo Wiki and Openbravo Issues

Openbravo actually runs Openbravo.com, Openbravo Issues, Openbravo Wiki, Openbravo Planet and other web properties to provide services to the Openbravo ecosystem. Nowadays, you have to log individually to every service, which requires authentication. ... [More] For example, you have to login in Mantis and to our Wiki separately since they work as separated systems. You also may use different usernames and passwords. This situation is going to get more complex as we introduce more web services that require authentication for a full user experience.

To address this situation we have been working on a Single Sign-On solution based on CAS. This will allow users to have a single username and password for all Openbravo web site. More convenient yet, when you are authenticated in one Openbravo web sites you are automatically authenticated into the rest of other sites.

We are planning to enter into production of Single Sign-On in Openbravo web sites by 4th of February 20.00 GMT.

Users affected with this migration will be notified by email with any required step that they have to perform.

If you have any issue login into the systems, please let us know sending an email to migration@openbravo.com, specifying your name, the email you entered at the time of registration, the username that you usually employ, and the problem you are experiencing.

Thanks for your support! [Less]

Openbravo ERP: 2.50alpha-r9 available

Openbravo ERP is a Web based ERP for SME, built on proven MVC & MDD framework that facilitate its customization. Already in production, Openbravo ERP encompasses a broad range of functionalities such as finance, supply chain, manufacturing & ... [More] much more

Featuring an exciting new modular architecture, usability improvements and broader functional coverage, Openbravo ERP 2.50 is the latest release of the leading open source ERP solution. This is an alpha version and it is intended for evaluation and stabilization purposes only. Openbravo 2.40 remains our best version for production usage. You cannot upgrade an existing system to 2.50alpha-r9 and you will not be able to upgrade a 2.50alpha-r9 instance to any subsequent version.

-- What is new --

For a list of feature included in this release, check the release notes:

http://wiki.openbravo.com/wiki/Openbravo_ERP_2.50_ReleaseNotes#New_Features

-- Test it --

We do encourage you to download and test this new version and give us your feedback. You can post your opinion and question on the new features in the Early Releases Discussion forum (http://sourceforge.net/forum/forum.php?forum_id=808030) and you can log any defect that you might find in the product using our issue tracking system (http://issues.openbravo.com).

In this release, you can install Openbravo ERP following two different approaches:

* Community Appliance (recommended): you can download and install a fully configured appliance that runs in your preferred virtualization environment. The appliance includes both Openbravo ERP as well as its underlaying technology stack and allows you to get started with Openbravo in just a few minutes and with only a few clicks. The images are available for the VMware, VirtualBox, QEMU, Parallels and Xen virtualization systems. To download these images:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783

* Custom installation (experts only): a custom installation gives you full control over your deployment environment and allows you to choose your preferred configuration for the technology stack. However, it requires you to install and configure all components of the technology stack as well as compiling Openbravo ERP from sources. You can to obtain a copy of the source code by either:

- Downloading a source code tarball:

https://sourceforge.net/project/showfiles.php?group_id=162271&package_id=275783&release_id=657341

- Checking out the source code from the Openbravo Subversion repository

https://dev.openbravo.com/svn/openbravo/tags/r2.50alpha-r9/

Download and test it following our installation and configuration guide:

http://wiki.openbravo.com/wiki/Openbravo_ERP_Installation_2.50 (0 comments) [Less]