Risk on propagating Pinocchio developments
I'm very concert with the propagation of new developments of Pinocchio (not for v2.0.0) inside crocoddyl. I understand that this is a painful necessity for crocoddyl, however I believe that this isn't a moment for doing it.
1. We have disable CI jobs.
We have been already waiting a lot of time for Pinocchio v2.0.0 release. Really think that each passed minute is a risk for breaking something without any checking. It's very unpleasant joke that after waiting so much we propagate latest Pinocchio developments
2. Example of what we shouldn't do now
In !95 (merged), we indeed propagate Pinocchio latest developments (further than v2). This is a huge problem because we won't be able to enable CI jobs for the devel branch. Really? we need to wait more to enable CI jobs??
3. Team working policy
I strongly believe that our priority is having a solid Python software, and then to move to c++ code. Further improvements in Python efficiency are really low priority. Low priorities don't hurt if they don't affect main team efforts.
Additionally, I believe that devel branch has to be tested for our CI support. Any devel should break current code status.
4. How do we deal with this?
Well ... I guess we should have a meeting and make a decision about 3. Nonetheless, if you make a PR where some Pinocchio branch is needed, then you should put in the PR comment.