Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
At long last, let's do it. Mark it stable!
Comment | File | Size | Author |
---|---|---|---|
#2 | 2931165.patch | 368 bytes | heddn |
Comments
Comment #2
heddnComment #3
phenaproximaI'm not sure the package should be Migration. This will bring it in line with Migrate Plus and Migrate Tools (i.e., contrib), so it makes sense...just thought I'd call it out here. What do others think?
Comment #4
heddnI was asked why use 'Migration' for the package name. I did that because that's what it is. There's already precedent in core for assigning a package name that isn't 'core'. Locale and others use 'Multilingual'.
Comment #5
maxocub CreditAttribution: maxocub as a volunteer commentedI like Migration for the package. Beside the multilingual package, there's also the field types modules and web services modules that have there own packages where they could be mixed up with contrib modules.
Comment #6
quietone CreditAttribution: quietone as a volunteer commentedMy two cents: I like 'Migration' as well.
Comment #7
Gábor HojtsyI agree this is a bunch of modules in core that are related and do have tightly related contribs as well. As per #2859225: [policy, no patch] Mark Migrate (not Migrate Drupal) as Stable we should mark RC, but then this issue has stable. Can we agree in #2859225: [policy, no patch] Mark Migrate (not Migrate Drupal) as Stable to mark stable right away? Sounds like there was no concerns that would warrant it to be RC.
Comment #8
heddnI've updated the title and wording in the policy issue.
Comment #9
heddnI think this can go back to NR?
Comment #10
heddnComment #11
phenaproximaAlright; I'm OK with Migration as the package name.
Comment #12
masipila CreditAttribution: masipila as a volunteer commentedMigration is also my preference for the package name.
Comment #13
maxocub CreditAttribution: maxocub as a volunteer commentedAs mentioned in the policy issue, I think the Migrate API is ready to go stable. I think we discussed in one of our meetings with either @xjm or @webchick that avoiding RC was OK here.
So I think this patch is ready.
Comment #14
phenaproxima*deep breath*
Comment #15
xjmThis is a really exciting milestone. :) (Advanced apologies if I don't tweet and cheer and announce publicly just yet; I'm pretty sure most people will not understand the nuance between "Migrate" and "Migrate Drupal" so I would not want them to misunderstand and run into problems because of it.) I think "Migration" is probably fine as a package name.
This has been discussed in #2859225: [policy, no patch] Mark Migrate (not Migrate Drupal) as Stable and by the committer team last month. @Gábor Hojtsy confirmed with the team that there are no additional things requiring BC breaks for the Migrate API. Also just going to repeat here what @catch wrote:
Going to check with him one more time before committing.
Comment #16
xjmOK, committed and pushed to 8.6.x and cherry-picked to 8.5.x. Yay!
Comment #17
xjmVCS integration is a bit backlogged presumably from 8.6.x being branched, but the commits are there in the main repo. :)
Comment #18
mikeryanCongrats to everyone who pushed this over the finish line!
Comment #19
larowlanfixing status
congrats all!
Comment #20
heddnStats of how what took to get here (as of 2017/01/11)
Thank you EVERYONE!