The code is actually supposed to improve testing but I do understand your concern. As a compromise, would it be ok to do an intermediate merge proposal where we just change the directory structure to reflect the upcoming changes with the library? This would ease our pain as well. Regarding to the release, we can do a release from any version in the code base and there's no real reason why the release schedule should stall progress. -- https://code.launchpad.net/~hipl-core/hipl/libhip/+merge/97589 Your team HIPL core team is subscribed to branch lp:hipl.