Hello all, it’s time for the weekly migration initiative meeting. The meeting will take place in slack in various threads

This meeting:
➤ Is for core migrate maintainers and developers and anybody else in the community with an interest in migrations
➤ Usually happens every Thursday and alternates between 1400 and 2100 UTC.
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ Has a public agenda anyone can add to here.
➤*Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.

0️⃣ Who is here this week? Introduce yourself.

heddn heddn, migrate maintainer
mikelutz Mike, migrate maintainer
alison Alison! User, helper, sometimes contributor, Bills fan.

1️⃣ Topics for discussion?  We’ll triage the issue queue, but what else?

2️⃣ D7 to D8 Book Migration “SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry”

mikelutz #3010123: D7 to D8 Book Migration "SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry"
heddn this still needs tests
Gábor Hojtsy (he/him) hm, there was another book bug, is this related

3️⃣ Use the lock service for migration locks

mikelutz #3066277: Use the lock service for migration locks
mikelutz This one has been sitting for a while.. I have my reservations on it, but we need to make a decision one way or another.
heddn Commented
mikelutz I think that constructor change is BC compatible, @heddn
mikelutz it’s an optional end parameter with a backup getter.
heddn @mikelutz ok, but that's now how its done right now.
mikelutz It’s not?  It’s not done how I would like, I’d rather set the member from the container in the constructor if it’s not passed in rather than having a getter not named ’getLock()’, but I don’t see how it isn’t at least BC compatible.
mikelutz Or do you just mean the tools Executable won’t be compatible with the lock system in general because it doesn’t implement it?
mikelutz I think I’m +1 for the ability to use the lock system now, but It definitly needs to be done in a way that doesn’t break tools before we have a chance to update.

4️⃣ Create Migration Lookup service

mikelutz #3004927: Create Migration Lookup and Stub services
mikelutz Still just looking for a thumbs up thumbs down on the interfaces/ new services from fellow maintainers before I do cleanup and write the rest of the tests. (edited)
heddn commented

5️⃣ Boolean Field On and Off Label not Migrating (edited) 

mikelutz #3067889: Boolean Field On and Off Label not Migrating
mikelutz I RTBCd this one.

6️⃣ Migrate UI - review help text

mikelutz #2939328: Migrate UI - review help text
alison I'll review (edited)
heddn commented
alison @heddn What's "fqdn" -- or is that out of the scope of this issue?
heddn @alison that why I gave an example in my comment. fqdn means fully qualified domain name. but examples don't need explanations if the example is good enough.
mikelutz FQDN stands for fully qualified domain name
alison ohhh ok i get it now, i mixed myself up reading the quote from the patch and your suggestion below the quote -- no good reason why, i just did :slightly_smiling_face: thanks! (edited)

Participants:

heddn, mikelutz, alison, Gábor Hojtsy (he/him)

Comments

mikelutz created an issue. See original summary.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Issue summary: View changes

quietone credited alison.

quietone credited heddn.

quietone’s picture

quietone’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

quietone’s picture

On Slack, alison told me that her d.o name is alisonjo315 not alison. So, I am correcting the credit.