Here is an update on the integration of RepEx with EnTK.
Code: I have started work on the code in two branches: in RepEx repo this is feature/enmd branch (https://github.com/radical-cybertools/radical.repex/tree/feature/enmd). In EnTK repo this is feature/repex branch (https://github.com/radical-cybertools/radical.ensemblemd/tree/feature/repex). feature/repex is based off the current master branch and I guess some effort will be needed to make it in sync with devel branch of EnTK. In terms of the code migration there are still some "minor" tasks which have to be finished, for example migration of asynchronous execution plug-in (EMM in RepEx). I hope you will let me finish these tasks.
Release planning: After action 1 will be done, we can plan releases. as I have mentioned before, EnTK has to be released before RepEx, since RepEx is relying on EnTK. Vivek: can you please provide an estimate when you are planning a new release?
Testing: an iteration on the tests developed by Suvigya is needed. These tests will not work with the new release of RepEx. I am not sure if these tests should be a part of 3.0 release or the next one. In addition, test results of RepEx 2.10 and RepEx 3.0 should be compared.
Performance profiling: After RepEx 3.0 is released it should be co
Here is an update on the integration of RepEx with EnTK.
Code: I have started work on the code in two branches: in RepEx repo this is feature/enmd branch (https://github.com/radical-cybertools/radical.repex/tree/feature/enmd). In EnTK repo this is feature/repex branch (https://github.com/radical-cybertools/radical.ensemblemd/tree/feature/repex). feature/repex is based off the current master branch and I guess some effort will be needed to make it in sync with devel branch of EnTK. In terms of the code migration there are still some "minor" tasks which have to be finished, for example migration of asynchronous execution plug-in (EMM in RepEx). I hope you will let me finish these tasks.
Release planning: After action 1 will be done, we can plan releases. as I have mentioned before, EnTK has to be released before RepEx, since RepEx is relying on EnTK. Vivek: can you please provide an estimate when you are planning a new release?
Testing: an iteration on the tests developed by Suvigya is needed. These tests will not work with the new release of RepEx. I am not sure if these tests should be a part of 3.0 release or the next one. In addition, test results of RepEx 2.10 and RepEx 3.0 should be compared.
Performance profiling: After RepEx 3.0 is released it should be co