permission to merge odeint to trunk
Can I still merge the develop branch of odeint into the master? The develop branch compiles fine and the tests are running for some time now. I also guess that no other boost libraries depend on odeint, so it should be relatively safe to merge it. Btw. there were no announcements that the master branch closes for the release, so I thought there is still some time to merge develop into master. But it seems that the release of Boost 1.56 has gained momentum and I don't want to silently merge into master.
Ping Come on guys. What do you think can I merge this changes. There are some new features which deserve to be in boost. On 08.07.2014 21:19, Karsten Ahnert wrote:
Can I still merge the develop branch of odeint into the master? The develop branch compiles fine and the tests are running for some time now. I also guess that no other boost libraries depend on odeint, so it should be relatively safe to merge it.
Btw. there were no announcements that the master branch closes for the release, so I thought there is still some time to merge develop into master. But it seems that the release of Boost 1.56 has gained momentum and I don't want to silently merge into master.
On 9 July 2014 21:14, Karsten Ahnert
Can I still merge the develop branch of odeint into the master? The develop branch compiles fine and the tests are running for some time now. I also guess that no other boost libraries depend on odeint, so it should be relatively safe to merge it.
There are quite a lot of new test failures, especially on Visual C++.
participants (2)
-
Daniel James -
Karsten Ahnert