Odoo - The current checkout of upstream Odoo

Age	Commit message (Collapse)	Author
2015-10-01	[MERGE] forward port of branch saas-6 up to e9f1ee4	Christophe Simonis

2015-09-30	[MERGE] Forward-port 8.0 up to rev. 26d0fe6d9f645ec128182bb2f4f8b9808ad05004	Olivier Dony

2015-09-28	[FIX] base_import_module: special chars in error messages	Arnaud Pineux
	use ustr() instead of str() to avoid traceback with translations Closes #4272
2015-08-31	[ADD] base_import_module: add boolean field `imported` on `ir.module.module`	Thomas Groutars

2015-01-16	[IMP] Cleanup and refactoring of exception handling	Goffin Simon
	Unify and refactor exception handling in framework and addons. The generic `except_osv` is now deprecated, and replaced by more specialized exception subtypes: - `UserError` (renamed from Warning, as it conflicts with the built-in `Warning`) raised when a non-technical error occurs during a business operation. It could be a missing information in the data provided by the user, or a misconfiguration. - `AccessError`: raised when any operation is denied because the user conducting it does not have the required access rights. - `AccessDenied`: raised when an operation that requires authenticated access is attempted via an unauthenticated request. - `MissingError`: raised when an operation is attempted on a record that does not exist. - `ValidationError`: raised when an operation violates a SQL or Python constraint. - All other exceptions are internal errors due to a system problem or bug, and raised untouched to the client-side, which should display a traceback. All exceptions take a single message argument. The `test_exceptions` module has been updated to showcase both new and old (deprecated) exceptions. A great many old `except_osv` had a useless title with "Error!" or "Warning", those have been removed, as this is handled by the client-side widget that displays the messages. This commit introduces a more consistent policy for logging errors and warnings: - All messages that do not require administrator attention should be logged at INFO level or lower. This includes all errors that are notified to the user in a friendly manner, even for access right problems or validation errors during business operations. - All messages that indicate a likely misconfiguration or malicious use by the users should be logged at WARNING level, as they typically require administrator attention. - All other unhandled internal errors cannot typically be handled by the user and should be logged at ERROR or higher level, as they require immediate administrator attention.
2014-09-05	[FIX] Some fixes for base_import_module	Fabien Meghazi
	- Properly check unmet dependencies - Set imported module's state to 'installed' - Fix bad translation usage
2014-06-11	Added --force to odoo deploy	Fabien Meghazi
	Will force --init mode even if module is already installed
2014-05-22	[IMP] improved code to show import result in wizard and improved typo	tpa-odoo

2014-05-22	[ADD] add wizard to import zipped module	tpa-odoo

2014-03-24	[IMP] Properly import files	Fabien Meghazi
	bzr revid: fme@openerp.com-20140324151711-89mfg14573dpnh0p
2014-03-20	[IMP] static file injected in ir.attachment	Fabien Meghazi
	bzr revid: fme@openerp.com-20140320143346-nimxg7c61lm1253x
2014-03-19	[WIP] base_import_module	Fabien Meghazi
	bzr revid: fme@openerp.com-20140319085343-zkee3rmqc9dzpa7h