[meta] Search API 8.x path to its home repository

Assuming that we aim to release a beta version of Search API 8.x when we move to the proper project repository, I'm going to change this issue to the meta format used by core for its various subsystems.

Since we still want to make (a lot of) API changes after moving the project to its normal repository, I think we'll just create alpha releases at that point. Beta will start once those API changes are in place, too.

I think a lowercase "meta" is more common?

Huh, interesting, didn't know about the [#NID@] thing.

Always more, sorry. Not only indexed items, but also returned results should use proper OOP.

One more down!

Little clean-up.

Also, D8 experts: see the new comments in #2235381: Fix config schema and #2252421: Adapt class names and namespaces to core standards.

Moved #2252171: Port Views integration to "Already done".

Only the processors now …

To avoid major blocks due to the last few processors / tests, I now opened up #2242361: Coding standards clean up and #2252421: Adapt class names and namespaces to core standards.

With #2230881: Tests for all Processors finally fixed, we are now free to finally start the move, resp. its associated tasks:

• #2242361: Coding standards clean up
• #2252421: Adapt class names and namespaces to core standards

Not yet in the list here, but #2253831: Make sure adding items to the tracking table for new indexes is scalable is a very important task, it's also the only one that is critical now, apart from this meta.

I don't really care if that happens before or after the move.

Didn't find time yet to look into it myself unfortunately :(

Yes, that definitely needs to happen, but I also think it can wait until after the move (unless someone wants to work on it now – and doesn't mind merge conflicts if they clash with someone doing a cleanup). It probably necessitates an API change, so has to happen before Beta, but it should be restricted to few enough files.

But if you have a few minutes, could you (or some other D8 whiz) maybe look at #2252421: Adapt class names and namespaces to core standards and see what still makes sense there?

Added some release info from #9 to the main post.

Added #2354271: Rename the "combined ID" separator (|) as a TODO before moving. Please, could everyone quickly go there and vote for something?

OK, I'm just doing some final clean-ups, then renaming the classes (#2242361: Coding standards clean up) and then doing the actual move.
(I'll then probably also create the first Alpha right away.)
So, just to warn you, it is probably not safe at the moment to do anything.

I'm not sure if we should create a first alpha already if showing separate fields in views is not possible yet? And I mean drupal entity render views, not specifically external fields.

Of course a lot is still missing, and it wouldn't be advisable to use it in production, yet (also because of some larger changes/additions still to come) – but that's more or less what "Alpha" means, right? Basically usable, but only for production if you want to be hardcore.

Just committed #2252421: Adapt class names and namespaces to core standards, so this is now finally good to go.
Only thing left to do is fight Git to the death until it lets me the complete history from sandbox:master to origin:8.x-1.x …

Wow, that was incredibly easy.

$ git checkout 8.x-1.x
$ rm -rf *
$ git add -A
$ git commit -m 'Removed the complete code so far to ease merging in the sandbox code.'
$ git merge master

So, finally fixed! Just waiting for the test bot now to verify (hopefully) that the 8.x-1.x branch is working, then I'll create the first alpha.
Things left to do:

• Move all the open, non-fixed issues from the sandbox to the normal project.
• Re-open all search_api and search_api_db issues of the last 15 months to see if they need to be ported – JOY! (I probably could've handled that better …)