Following 2 simultaneous queries from larry and drafnor today, I thought I'd let you know what the story is with this idea.

I do realize that having it 4.6 will dissuade a few of the movers and shakers at Drupal from looking too hard at it for now. (maybe that's not a bad thing)
But the fact is a large driving force is to develop a tool for some real-world clients (or three) who have already commited to 4.6 and need it done there. So this is my first priority.

I will indeed look at shifting it forward to 4.7, but not immediately. I need to sit down for a bit and grok the new 'best practices' for migration, I want to do it right, and I'm not touching it until it's ready to go.

Hopefully, I've modularized my code chunks to the point that not too much work will be needed. I'll continue reviewing the code to try and put all the forms bits in one file, leaving the engine (and others concept) in their own libraries. I'm pretty sure it's mostly like that at the moment, so hopefully only that one interface library will have to fork, while the rest of it works and gets improved on for both versions.

- see, 'best practices' :-B

Watch this space for updates.
.dan.

Comments

eaton’s picture

Feel free to drop me a line if you're interested in talking about/planning for the 4.7 migration. Your module suite looks VERY useful, and I'm curious about the potential for integration with other modules as well. Great work so far.

DuaelFr’s picture

Status: Postponed » Closed (won't fix)

This version of Relationship is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.