The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

Drupal 8 progress from my / MongoDB perspective: update #7

Submitted by nk on Mon, 2012-11-12 22:39

The new DrupalKernel patch is ready. This will unify the bootstrap and the "real" service container and compile them to disk. Very important for us. Also, I had a rift with another developer for too long but in this issue we finally managed (although it's visible we both struggled) to work together and get to an agreement. I am very hopeful this trend continues.

The new batch API requires a "move to the back operation" which in turn requires a new database layer feature (or fixes a database bug, what do you classify "SQL supports subselects as update values but DBTNG doesn't"?), both are ready.

I have a working patch for relationships with Entity Query. It uses the new entity API which is not really wildspread yet: only a test entity and the text fields are converted so the field part of it is sadly untested. It also badly needs polish, right now it's in the "it was hard to write, it should be hard to read" state.

Seems the core committers have a sane approach to the 'feature freeze' so it won't affect me greatly.

Two days ago the menu_links as entities patch from amateescu reached green, fabolous news. With all said and done, I see very nice progress.

Next up for me are finishing entity query relationships, bringing the new batch API to a committable state. Perhaps poke at the entity storage.

Commenting on this Story is closed.

Submitted by Anonymous on Thu, 2012-11-29 22:19.

Isn't it update #7?

Submitted by nk on Fri, 2012-11-30 05:49.