This change adds a simple way to record debug messages while creating or testing server actions. It helps administrators and implementers understand what automated actions are doing, making setup and troubleshooting faster without affecting everyday users.

...building server action

Example of use in server action:
log('Message: %s' % obj.name)

The CRM lead list now shows the company name as a separate column. This makes it easier for sales teams to identify and sort leads by organization without opening each lead record.

This update makes a small correction to the project's README documentation. It helps keep public project information accurate and easier to follow, with no expected impact on product behavior.

This fixes an issue where switching between views could leave empty page containers visible when no controller was attached. Users should see cleaner, more consistent screens without stray blank areas caused by styling.

The view manager upon switch won't properly hide the empty `div` container for other views when they don't already have a controller.

CSS might then show these div quite easily.

It seems pretty obvious that they should be hidden properly even if empty.

This update corrects the alignment of the Weight field on the stock move form. It makes the form display more consistently, reducing visual confusion for users working with delivery or inventory details.

Hello,

Fixed the Issue #541 (#541)
In stock move form set the group alignment on "Weight " field.

Thanks.

This fixes a missing field on sales order lines related to bill of materials options. It ensures sales users can see and use the expected product properties when working with manufacturing-related sales orders.

I guess  the `property_ids` field has been left behind when moving the filed from `sale_stock` to `sale_mrp`.

A missing internal translation helper and service import were added to the common server service. This prevents errors in the about information workflow and keeps the server service loading reliably.

Add missing 'openerp.tools.translate._' function for the 'exp_about()' method and add relative import for the 'openerp.service.security' module.

Incoming emails are now matched to contacts using a stricter email comparison. This helps prevent messages from being linked to the wrong customer when similar email addresses exist.

The current operator is ilike but it add wildcards around right criteria so we can have false positive.

eg. I' have an email in my customer base like a_mail@provider.com

If I get a mail from mail@provider.com as ilike operator uses wildcards a_mail@provider.com can potentially be matched and retrun a faulty match.