Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Remove core/description and use external repo. #7022
Conversation
anastasiamac
approved these changes
Feb 23, 2017
The change itself is awesome \o/
My concern is with the process, especially updates/deletes/additions...
I wonder how we can stay in sync, i.e. how we can ensure that we do not forget to update this external package when we change core structures.
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
The general rule there is to have a test that the two are in sync. It's ok
for tests to cross pollinate as long as the code itself doesn't.
Didn't we have one that would fail if you added/changed a database doc
without updating the description?
John
=:->
…
|
|
Ugh, I guess that means the changes I'm making to add remote applications to the description need to happen there now. |
|
Build failed: Tests failed |
|
$$windows-mongo$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
We have tests in the state package to make sure things are migrated. The serialisation format is separate. |
|
Build failed: Tests failed |
|
$$intermittent-windows-again$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
howbazaar commentedFeb 23, 2017
Use the new extraced juju/description package.