Plan for Entity Translation 7.x-1.0 release

Well, your timing is perfect :)

I was waiting to release the second alpha because of the ongoing work to revamp the translation UI (see #1282018: Improve UX of language-aware entity forms). The core patch the new UI relies on (#1495648: Introduce entity language support) has been committed today, so a new alpha is coming very soon. My plan is to release alpha-2 with the old UI, to avoid forcing people to adopt the new UI to get all the latest improvements. Then the new UI will be committed to the (soon to be created) 7.x-1.x branch, as it should be pretty stable (I'm using it on three production sites already).

[text moved to the OP]

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Added a few more issues

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Added the Commerce integration issue.

As for the “Redirect integration”, if you introduce CRUD hooks shouldn't Redirect implement those and thus integrate with Entity Translation from it's side?

I expect this issue to be very similar to the Pathauto one.

The new alpha has been released. I will wait some more days to see if some nasty bug comes up before initating the 7.x-1.x branch.

Updated issue summary with road map.

The new UI has been committed!

Updated issue summary.

Thank you @plach!

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

We are really close to beta1. See the OP :)

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Ok, we are mostly ready for the first beta. I don't know whether we will be able to fix comments soon, since that one is blocked on a core issue and nobody cares about D7 core with the D8 feature freeze approaching. We should really get the Commerce integration issue RTBC as soon as possible, though.

Updated issue summary.

Updated issue summary.

Updated issue summary.

Added #1799770

Updated issue summary

The last blocker has been committed right now! Let's kill those new bugs that appeared in the queue in the last days and release beta1!

Updated issue summary.

Ladies and gentlemen, beta1 is finally out! I expect beta2 to be released soon with a lot of bug fixes :)

We should totally focus on test coverage now.

Entity Translation 7.x-1.0-beta1
Error
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'module' cannot be null: INSERT INTO {role_permission} (rid, permission, module) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 2 [:db_insert_placeholder_1] => edit node original values [:db_insert_placeholder_2] => ) в функции user_role_grant_permissions() (строка 3043 в файле /home/cp735535/public_html/modules/user/user.module).

Updated issue summary.

@DD85:

This is definitely not the place to report bugs. You should probably have a look to #1829980: Upgrade to Beta1 results in "Integrity constraint violation: 1048 Column 'module' cannot be null".

Updated issue summary.

@bforchhammer:

I think now it's a good time to release beta2, ok?

@plach: yes, sounds good.

I'm also adding #1829630: Improve workflow permissions (match D8 solution) to the list above; let's try to get permissions sorted out for beta3.

Updated issue summary.

Sure, I am planning to have "even" betas shipping only bug fixes and major/critical tasks and "odd" betas with features.

beta2 is out :)

Added issue #1829630 (permissions)

Removed Redirect integration which works just fine :)

trying translation redirect, it does nothing, i see:

http://drupal.org/node/1280468

it said to be based on implementation of hook_i18n_translate_path, is it there?

@bforchhammer:

Since development is not going on as fast as I'd hope and we have lots of bug fixes, I'd like to release beta3 soon and then commit #1865244: Allow multiple translation handlers on the same form to start testing it a bit more. What do you think?

Updated issue summary.

@plach: Sounds good. I agree that #1865244: Allow multiple translation handlers on the same form should be tested by more people, so that seems like a good way to go forward.

I am sorry I haven't found as much time for ET as I'd like to over the past months; the big issue on my personal list is still #1829630: Improve workflow permissions (match D8 solution).

I am sorry I haven't found as much time for ET as I'd like to over the past months

I absolutely wasn't referring to you :) I found little time for ET either, I am totally busy with D8 right now. Also #1829630: Improve workflow permissions (match D8 solution) definitely needs a some dev-release testing before being released...

The third beta is out :)

Great news @plach, thank you!

Awesome, thanks! :)

Updated issue summary.

[wrong issue, sorry]

Updated issue summary.

Updated issue summary

:) thanks

Are there plans for more bigger changes in this module before a first release?

I plan to do some work now to upgrade from beta3 to get the revision, would be great to know if it is worth to wait a little bit before upgrading? Especially thinking about a D8 upgrade later.

No, I'm not planning to do anything else.

I see there's quite a lot still to do before a 1.0.

Could we get a new beta release in the meantime? The current beta is from January, and patches in the issue queue won't apply to it, which makes it harder to work with production sites.

(BTW, this Drush plugin writes release notes for you, which makes the whole process of rolling a release take no more than a couple of minutes: https://www.drupal.org/project/grn)

Yes, it would be nice to have 7.x-1.0-beta5 with patches and an announcement that you are seeking a co-mantainer... Thanks for so much work :)

#1291388: Add support for multilingual core search got in, one less task towards release. At this point I think the main blockers are the two taxonomy issues and the test coverage one. I'll try push those forward in the next weeks so we can finally have a stable release.

I updated from 7.x-1.0-beta3+7-dev to 7.x-1.0-beta5 and all updates run perfect. I have being creating nodes on my different content types, translating, deleting and everything works perfect (besides things that are not upgraded here and are in the issue cue).

I will try next Saturday to test some patches. Now I can't because it looks that my computer is dying and I have to reinstall.

Grazie tanto :)

Thank you :)

Today I updated a Commerce Kickstart 7.x-2.36 and make some test too and everything works :)

@plach I can test Saturday the 2 patches with taxonomy here (the test coverage is beyond my knowledge...). I thought to review the patches that are in the cue ... and make comments for other people to test. It would be a small collaboration to clean the issue cue. I mean some from here (the ones that doesn't require me to change much my configuration or that I am able to test):

https://www.drupal.org/project/issues/entity_translation?text=&status=8&...

Would you include any other patches? I don't want to ask if you don't have the time... :) Is there any other thing that you would like me to test? Or any in the cue with "needs review" that you consider preferent? Bugs better than feature request? I will not be able to make all.

Have a good coding :)

@candelas:

Thank you so much for your help, it's really appreciated :)

The issue queue badly needs some clean-up/triaging and anything you can do is welcome!

Roughly my plans for the upcoming work are the following: I'd like to focus on the two taxonomy issues and commit them as soon as possible. Once we get there I'd wish to tag the first RC and start focusing on bug fixes and critical/major tasks only. Basically after RC1 features would be more or less "frozen", unless the chance to introduce regressions or technical debt are very low. After 1.0 features would be unfrozen and a new cycle will begin. Hopefully the path towards 1.1 will be more agile and less painful, but this will heavily depend on how much help I'll get, because lately I've not been working on D7 multilingual projects so much, thus all the time I spend on ET is taken from my spare time (and I don't get too much of that either lately).

:)
I don't understand what you mean by RC (I am learning now programming with Java in Catalan language and there are many words in English that I don't know).

What I was thinking, since I have not time/knowledge to review all the cue, is to comment in the "needs review" issues that you were working and that it is a good moment to test. But I didn't want to ask if that work is not going to be used now.

I think it would be very useful that when a module developer is working on a new release, people that has committed a patch or is in comments would receive an email so they could put a bit of time to help testing. So I was offering to make this manually :)

If you say ok, I make today those comments, so people gets the alert. Also I will add that a coo-maintainer is badly needed ;) I wish I had the knowledge because for a junior developer is a perfect opportunity to learn from you. Also this module will be very important to migrate multilingual sites to Drupal 8, I believe. So, for what I understand, I wait for 1.0 to write those comments, don't I?

One less: #1661348: I18n Taxonomy integration

@candelas:

RC means "release candidate", i.e. a version that could be released as stable, unless there are critical problems with it, which would require a new RC fixing them to be rolled.

And also #1344672: Field Collection: Field translation (entity_translation) support. is gone!

All stable release blockers gone!

wow, great work!
beta7 is already extremely good.

so 1.0 soon?

Yes, if no critical issue is opened, I guess in a couple of weeks we could have a stable release :)

And here it is :)

https://www.drupal.org/project/entity_translation/releases/7.x-1.0

Thanks to every one that helped to make this happen!

Thanks Plach! very high quality release. Great job on the automated (simpletest) tests.

This is amazing work, thank you plach and everyone who contributed!