-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
next release #136
Comments
I'll double-check that code in the next couple days. |
Ok thanks!
…On Tue, Mar 27, 2018 at 9:06 AM TJ Mahr ***@***.***> wrote:
I'll double-check that code in the next couple days.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHb4QzHFP7v0q6A35E-jIwBo9x_Gzrphks5tijljgaJpZM4S73QA>
.
|
I think the code should be okay, based on tests in #137. |
Ok great, thanks! I'll go ahead and get the release submitted. |
closing after submitting version 1.5.0. I'll tag a release when accepted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@tjmahr I'd like to release the loo update stuff since we'll be releasing a new version of the loo package asap. We've also got a bunch of other things waiting so probably a good time to get something out anyway. Do I need to do anything with the
ppc_data
function that's on the master branch? Is that intended for/ready for release? Or do we need to remove that code before releasing from master branch?The text was updated successfully, but these errors were encountered: