Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
During the #2230861: Scrum discussion 01 April 2014 we've decided to resume using the Search API project repository once basic functionality and features are working.
Once it has moved it will be in alpha release phase, with API changes still to come.
The following issues should be done before switching:
Current tasks
- None
Nice-to-have or do later
- #2256219: Allow the content entity datasource to specify which languages to handle
- #2242321: Optimize the tracker plugin (or add a new one)
Already done!
- #2244787: Ensure index state invariants always hold
- #2232253: Make the indexing batch process work
- #2230931: Supporting multiple item types per index
- #2231739: Make it possible to index with other roles
- #2249011: Port Search API DB to 8.x
- #2230887: UI Indexing flow should be tested
- #2241429: Support translations
- #2242493: Use exceptions instead of "return FALSE;"
- #2252171: Port Views integration
- #2253237: Add proper classes for indexed items and search results
- #2235381: Fix config schema
- #2230925: Implement server tasks system
- #2230881: Tests for all Processors
- #2242361: Coding standards clean up
- #2354271: Rename the "combined ID" separator (|)
- #2252421: Adapt class names and namespaces to core standards
Comments
Comment #1
drunken monkeyComment #2
freblasty CreditAttribution: freblasty commentedComment #3
freblasty CreditAttribution: freblasty commentedComment #4
amateescu CreditAttribution: amateescu commentedAssuming 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.
Comment #5
amateescu CreditAttribution: amateescu commentedComment #6
Nick_vhComment #7
Nick_vhComment #8
amateescu CreditAttribution: amateescu commentedComment #9
drunken monkeySince 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.
Comment #10
drunken monkeyI think a lowercase "meta" is more common?
Comment #11
drunken monkeyHuh, interesting, didn't know about the
[#NID@]
thing.Comment #12
drunken monkeyComment #13
drunken monkeyAlways more, sorry. Not only indexed items, but also returned results should use proper OOP.
Comment #14
amateescu CreditAttribution: amateescu commentedComment #15
Nick_vhComment #16
Nick_vhComment #17
amateescu CreditAttribution: amateescu commentedComment #18
amateescu CreditAttribution: amateescu commentedOne more down!
Comment #19
drunken monkeyLittle clean-up.
Also, D8 experts: see the new comments in #2235381: Fix config schema and #2252421: Adapt class names and namespaces to core standards.
Comment #20
drunken monkeyComment #21
drunken monkeyMoved #2252171: Port Views integration to "Already done".
Comment #22
drunken monkeyComment #23
drunken monkeyComment #24
drunken monkeyOnly the processors now …
Comment #25
drunken monkeyTo 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.
Comment #26
drunken monkeyWith #2230881: Tests for all Processors finally fixed, we are now free to finally start the move, resp. its associated tasks:
Comment #27
drunken monkeyComment #28
BerdirNot 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 :(
Comment #29
drunken monkeyYes, 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?
Comment #30
rooby CreditAttribution: rooby commentedAdded some release info from #9 to the main post.
Comment #31
drunken monkeyAdded #2354271: Rename the "combined ID" separator (|) as a TODO before moving. Please, could everyone quickly go there and vote for something?
Comment #32
drunken monkeyOK, 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.
Comment #33
Nick_vhI'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.
Comment #34
drunken monkeyOf 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.
Comment #35
drunken monkeyJust 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 deathuntil it lets me the complete history fromsandbox:master
toorigin:8.x-1.x
…Comment #36
drunken monkeyWow, that was incredibly easy.
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: