Closed tomschenkjr closed 7 years ago
Yes, I've been wondering how to do this.
The rversion
branch was initially experimental and I started it with the intention of replicating the python work. So, I actually continued to develop the maps and other "permanent" things in the main branch. So, I have some work to make sure that's incorporated.
The other issue is whether I should completely blow away the python version. At this point I think it's fair to say that we won't be using it, but it might be worth keeping on a separate branch?
The first part will need to be done.
For the second part—preserving the python code—just create a releasehttps://github.com/Chicago/WNV_model/releases, which will essentially bookmark the code. Once the R code is in the master
branch, then create a new release with a higher version number.
From: Gene Leynes [mailto:notifications@github.com] Sent: Friday, May 19, 2017 4:14 PM To: Chicago/WNV_model WNV_model@noreply.github.com Cc: Schenk, Tom Tom.Schenk@cityofchicago.org; Author author@noreply.github.com Subject: Re: [Chicago/WNV_model] Move production code to Master branch (#22)
Yes, I've been wondering how to do this.
The rversion branch was initially experimental and I started it with the intention of replicating the python work. So, I actually continued to develop the maps and other "permanent" things in the main branch. So, I have some work to make sure that's incorporated.
The other issue is whether I should completely blow away the python version. At this point I think it's fair to say that we won't be using it, but it might be worth keeping on a separate branch?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Chicago/WNV_model/issues/22#issuecomment-302812653, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkC0V28W7jwhNUkdRRTf8tyHo25X2kwks5r7gYFgaJpZM4NhA4M.
This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), you are hereby notified that any dissemination, distribution, printing or copying of this e-mail, and any attachment thereto, is strictly prohibited. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the original and any copy of any e-mail and printout thereof.
I moved it over, but I have to write the README.md, add metadata, etc. Also, I'm planning to test on the dev server.
Looks good, closing this issue.
Discussion on supporting documentation can continue over in #34.
It seems the code actively under development is under the
rversion
of the code. This should be promoted tomaster
branch as it's the standard practice and begin to align branching habits to the team's typical naming conventions.