We need to split repositories between Nastya, Debra and modules. This would allow us to have a nice separation between common code and robot code, while still being easy to integrate, thanks to hg submodules.
It need to be done cleanly, because we want to keep history of the project. We can do that using hg convert with a filemap[1].
I wrote the beginning of a script to do that. It still needs to be tested and documented before deployement. See attachement for details.
We also need a way to transmit issues. According to [2] we can export issues. We need to investigate if we are able to filter issues by component or if we need to write our own filter using the information available in [3].
We need to split repositories between Nastya, Debra and
modules
. This would allow us to have a nice separation between common code and robot code, while still being easy to integrate, thanks to hg submodules.It need to be done cleanly, because we want to keep history of the project. We can do that using hg convert with a filemap[1].
I wrote the beginning of a script to do that. It still needs to be tested and documented before deployement. See attachement for details.
We also need a way to transmit issues. According to [2] we can export issues. We need to investigate if we are able to filter issues by component or if we need to write our own filter using the information available in [3].
[1] http://mercurial.selenic.com/wiki/ConvertExtension#A--filemap
[2] http://blog.bitbucket.org/2013/04/02/finnovation-brings-you-a-heap-of-new-features/
[3] https://confluence.atlassian.com/pages/viewpage.action?pageId=330796872