Move us officially over to Next Generation #621
Comments
For boring historical reasons (which honestly weren't terribly compelling) we have our old december code co-existing with our vNext code. Once #811 passes and before we check in #740 we need to make this change (hopefully along with @artemjackson's work on #759).
Please make sure to use 'git mv' when moving or renaming things. And yes as you move stuff around all the paths have to be fixed up. I'd suggest using an IDE like WebStorm or IntelliJ that can figure a lot of this out for you automatically so you don't have to chase everything down. My other suggestion is that we will do #759 once this bug is done. Which again won't happen until #811 is checked in to vNext and you have finished #507 and we have merged #507 and #811 into vNext_yarong_417_1 (e.g. #740). Although I wonder how much easier this might be if we did #759 first? But I suspect we would have to do a lot of surgery on a lot of files before we saw any benefit and we don't have time for that right now. But talk to @artemjackson about it. |
About 20% done. |
I made an exception for:
We are still using
I moved
All files are used in bv_tests.
Yes, this test was just a bit outdated. I've fixed it. We can run it with |
Should be done today. |
Still working on 811 so that is blocking this. |
A few more hours of work to do so might slip to Monday. |
I've moved
We can implement good tests for
I think this can be saved. It was used instead of
I don't think we should delete
I've removed |
O.k. this looks reasonable to me. Just please file the issues to make sure we actually follow up on the various things you identified as needing to be investigated/re-written. |
We took a run at it, it kind of blew up. So we'll try again later when we have vNext stabilized and then we will have everyone shut out of vNext until we get this bug done. |
Take a quick pass to see which files we want to maintain over the transition
The text was updated successfully, but these errors were encountered: