-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration path to one-true source is unknown #16
Comments
actually, this is now the one true copy of the source:
there are still some additional internal bits that add internal-only functionality, and a bunch of integration tests. but for the source itself, this is the truth. as to helping: once i get some cycles, i'm planning to push the integration tests into this repo, and i'll need to set up travis to run them. i totally want to copy the gcloud-python setup for that. |
w00t So I'd say "close this", though I believe you've mentioned elsewhere that you are missing tests here that you run elsewhere. Maybe close this and file a bug for that? Or just rename here? |
i opened #17 for the tests. |
There are copies floating here, in https://github.com/craigcitro/apitools, "internal" in Google, in
gsutil
and possible elsewhere.Is there a migration plan in place? Is there a known set of features that differ? Is there a TODO list?
Most importantly: Can we (open source peoplez) help?
The text was updated successfully, but these errors were encountered: