Since beta1 Entity Translation requires core version at least 7.15.
Maintenance release. Primarily fixes the upgrade path from alpha2. See the beta1 release notes for a complete list of changes since alpha2.
#1846104: Entity Translation shouldn't assume $form['#entity_type'] is a string
#1845896: Validate translation authoring info on submit
#1835578: Entity translation metadata should be stored only if the entity bundle is translatable
#1437976: Invalid node translation menu callback set when entity translation for nodes is disabled
#1844844: Content type settings always showed
#1833496: Cannot initialize entity translation path variables (invalid path scheme).
#1397560: Delete translation button not working if destination parameter is set
#1829740: Node and comments ET settings are available also when translation is disabled
#1829980: Upgrade to Beta1 results in "Integrity constraint violation: 1048 Column 'module' cannot be null"
This release includes a huge number of new features and requires core at least 7.15. Many parts of the module changed since alpha2, hence you should backup your site and test it carefully when upgrading to ensure everything is still working for you.
This features a totally revamped translation UI (see #1282018: Improve UX of language-aware entity forms for details), which is using a language-aware entity form instead of a separate translation form. This allows to deal cleanly with modules adding new elements to the various entity forms. As a consequence the entity info needed to provide ET integration has slightly changed, check entity_translation.api.php to see if you need to adjust your code. Moreover
hook_translation_info() has gone in favor of plain
hook_entity_info() (see #1114410: Replace hook_translation_info() with hook_entity_info() ).
To replicate the behavior of the translation form shipped with alpha2 a new set of (optional) permissions have been introduced, see the related section in the Entity Translation guide.Read more
This is the last tagged release featuring a separate translation form. A new UI is coming with the following releases, see #1624830: [META] Roadmap for a stable release of Entity Translation for details.
#1230858: Compatibility with node_clone; entity_id of old node is used, resulting in integrity constraint violation
#1262512: Clear the entity cache after translate
#1280506: Simpletests broken after upgrading to D7.7
#1280660: Gracefully handle module being disabled and re-enabled
#1283200: Enable content language negotiation the right way
#1293638: Language fallback on Taxonomy Terms (or any entity type without locale support)
#1174242: Properly override the node/%node/translate menu router path
#1367832: Check #parents and #field_parents for source language in new translation form
#1380380: Prevent notice when translation has been removed from the form
#1432206: Loss of field content during translatability switch operation
#1519894: Entity translation upgrade migration incomplete
#1519898: The upgrade process may freeze
#1519906: Migrate aliases when upgrading nodes
#1519912: Empty stored values may mess up the translatable switch update
#1341314: Nested call of entity_get_info() due to menu_get_router() in entity_translation_entity_info_alter()
#1599568: No content is displayed if fallback is disabled and entity is set to 'Language Neutral'
#1587108: Error: The entities of type Taxonomy term do not define a valid base path: it will not be possible to translate them.
First tagged release. See #1271196: Please created tagged release ASAP (help integrating with other modules) for details.