-
Notifications
You must be signed in to change notification settings - Fork 3
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
Document SOP for updating the repo sh run.sh make update_repo
#435
Comments
What is the significance of Feb. 20? Is there an ODK release planned? Edit: I've read #433 (review) and see this is the case. |
Yes, thats right! |
From what I heard from Joe yesterday, this seems fine. |
Trish and I were basically planning on this, so I'm mostly in agreement. I'll add some thoughts in a bit. I was surprised to see that you merged #432. Based on what you've written in the OP, I'm guessing that currently |
Yes, for now dev is the way to go. |
Alright, the reason I didn't sign off on this yet is because I had this in the works. Please review first: |
This should now be documented based on using the ODK runner based on this comment. |
Sounds good! Updated the OP w/ new steps. |
New plan:
odkrunner
Action items:
odkrunner
#719Original plan (obsolete)
Until 20th February
This is using
run.sh.conf
which has all the relevant environment variables, includingODK_TAG=dev
. Contrary to what I told you @joeflack4 you cannot just passODK_TAG=dev
to run.sh, because run.sh.conf has precedence.After 20th February
src/ontology/run.sh.conf
and setODK_TAG=latest
src/ontology/run.sh.conf
and setODK_TAG=dev
The text was updated successfully, but these errors were encountered: