Mark Migrate (API) as stable

+++ b/core/modules/migrate/migrate.info.yml
@@ -1,6 +1,6 @@
+package: Migration

I'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?

I 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.

My two cents: I like 'Migration' as well.

I 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.

Alright; I'm OK with Migration as the package name.

Migration is also my preference for the package name.

As 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.

*deep breath*

This 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:

Although I think we should leave #2748609: [meta] Preserving auto-increment IDs on migration is fragile open, I also think the audit issue is enough to make it not block migrate being stable.

The only remaining concern I'd have is that it looks like we're going to need an API addition in order to resolve the translated node IDs issues, but that's absolutely going to be an API addition so bc shouldn't be an issue there.

Going to check with him one more time before committing.

OK, committed and pushed to 8.6.x and cherry-picked to 8.5.x. Yay!

VCS integration is a bit backlogged presumably from 8.6.x being branched, but the commits are there in the main repo. :)

Congrats to everyone who pushed this over the finish line!

fixing status

congrats all!