This page documents some differences on project organization between OpenERP and Tryton. In general we give for granted that you know more or less how OpenERP is organized.
On November, 2012 the Tryton Foundation was created in Belgium and with it its first Board of Directors. The Foundation is in some way in charge to replace the figure of OpenERP SA in the case of OpenERP. It is there to:
It also shows the world and specially end users and companies that the community is well organized. Companies tend to search for something solid and probably the Foundation is the way to make this clear while keeping the vendor independence they also desire.
Tryton includes data migration when a new version is installed. This is a clear advantage over OpenERP because the migration effort is shared between all participants. In OpenERP we can easily share modules, but migrations are not so easy to share and thus either users are locked to the editor or they have to spend a larger amount of money than they would if everything was included as in Tryton.
Tryton releases a new major version every 6 months and it is very regular. The reason is that the development version is kept very stable during the whole development process and new features are only added when they are ready, and in the last month no new features are added but is reserved for bug fixing.
Here's the list of all Tryton releases starting at 1.0 with its planned release dates and real release dates:
|Version||Planned Date||Real Date||Delay|
This predictability is a huge advantage for users and integrators because it allows proper planning of deployment of new versions.
In contrast, OpenERP follows a feature-based release cycle and usually releases too soon, because new features and big patches are applied only days before final release. This results in very unstable dot zero versions which tends to make experienced integrators wait several months before relying on them.
OpenERP and Tryton have similar but different licenses. OpenERP uses AGPLv3 while Tryton uses GPLv3.
The main difference is that if you make a development in OpenERP which can be considered a derivative work (a change on the client or a module will most probably be), and you give access to those changes to third parties such as customers or suppliers (or you provide some kind of SaaS) you must make the source code available to them.
The same is not true in Tryton and you're only forced to provide the source code if you distribute the application in binary form.
Both have advantages and drawbacks:
The former does not allow private (not publishing the code) SaaS except if that is provided by OpenERP SA who owns the code. This creates incentives to integrators to free their code and means there's a large number of modules available.
At the same time OpenERP SA has a double license model and you can acquire a proprietary version which will allow you to provide this SaaS, but of course, you will not be able to use most community modules unless the authors sell you proprietary licenses.
The latter will allow you to create your own modules without publishing the code to your customers and suppliers (which may also be your competitors).
At the same time it does not create incentives to publish the code although it gives more freedom to Tryton users.
Tryton takes security quite seriously: opens CVEs and makes special security releases if security issues are found.
In contrast, take for example this bug reported to OpenERP where the bug is marked as incomplete and several of the issues are still not fixed today more than two years later.