hr_timesheet_sheet: for attendance, set default value for employee_id in the context
[FIX] delivery: propagate additional fields in chained pickings

closes #367
[IMP] add an index on account_move_line(date, id)

fixes https://launchpad.net/bugs/1311004
[FIX] account: move translatable tag

The field note on account.fiscal.position and account.fiscal.position.template should not be translatable in classic modules.
The l10n_multilang module is intendend to make chart of accounts multilang and is the place to set translate=True
Merge pull request #411 from acsone/lp-1200611_lga

[FIX] hr_timesheet_sheet: correctly set the employee on the attendance
Merge pull request #413 from gurneyalex/7.0-fix_lp1025703-afe

[FIX] delivery: add missing information in chained pickings
Merge pull request #417 from gurneyalex/7.0-fix_1311004_account_move_line_index-afe

[IMP] account.move.line: extra index on (date, id) corresponding to the default _order, courtesy of @gurneyalex.

 Fixes https://bugs.launchpad.net/openobject-addons/+bug/1311004
[FIX] base_action_rule: do not force registry reload when writing on a rule unless really needed

Executing a rule always updates the `last_run` value, which would
always force a useless registry reload to occur. Only signal the
change if the rule applies to a model that was not previoulsy
monitored for base action rules.
[FIX] base_action_rule: do not repeatedly trigger already-executed rules based on time condition

A programming error introduced at rco@openerp.com-20121220142445-emzzvhlw400q37c9
fails to properly check when a rule has already been executed in the past.
Time-based rules should only be executed if the trigger date is in the past and:
 - either they never executed before
 - or the last execution date is older than the trigger date
[FIX] base_action_rule: prevent recursive rule trigger also when processing time-based rules

A safety guard already in place prevents the recursive
trigger of rules while another rule is being executed,
as a simple measure to prevent endless loops.
This guard was missing when processing time-based rules.
[FIX] base_action_rule: automatic commit during background processing of rules

This will make sure already processed rules are persisted
in case a timeout occurs while processing the next ones,
ensuring that *some* progress can be made in most cases.
[FIX] sale_order: set state field track_visibility

sale_order module override state field of sale.oder (sale.sale.py) and forgot to reset the track_visibility, therefore sale orders state changes are no longer tracked once this module installed.
parse_value: interger != float

Wwhen parsing a integer field, do not accept float values. '1' or '1.0' is ok but not '1.1'. (opw 608544)
[FIX] orm: avoir errors reading twice a field

_read_flat: remove duplicated fields in read call
get many2one: as False is instance of int, check the value of x first to avoid calling a name_get with a list of False

When we were reading twice a m2o field where at least one result is null, the first call to name_get would set the value to False instead of None and then accepted by the filter 'isinstance(x, (int,long))'
Merge pull request #506 from odoo-dev/7.0-read-duplicate-fields-mat

[MERGE] orm: avoids error when reading twice a field
[FIX] hr: typo in a field definition
[FIX] portal: typos in portal wall actions.