Hi Ewout, On 21 Feb 2013, at 12:48, Ewout wrote: > We would like to add some features to D2RQ. It would make sense to start from > the develop branch, as it contains a partial rewrite of the code. Adding > features on top of master seems like a waste now, because it would be > difficult to merge the changes when the develop branch becomes the master.
That's correct. > However, we noticed that a lot of the optimizations that are present on the > master branch, don't work on the develop branch (tested with --fast). ... > If so, where is the develop branch heading wrt query optimization? Is it > really the goal to replace QueryEngineD2RQ with something else? I'm working on finishing these parts of the new query engine as we speak. All optimizations of the old master branch will work on the new develop branch in the Very Near Future. I know that the current situation, where master is kind of obsolete, but develop doesn't quite work yet, is very awkward for anyone who wants to do work on the codebase. I apologize for this state of affairs. May I ask what parts of the code you are planning to work on? This would help me with allocating my time most effectively. Best, Richard ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ d2rq-map-devel mailing list d2rq-map-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/d2rq-map-devel
