You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #160, several of us discussed a potential release strategy. I'll break out this discussion in a new issue, where we can continue a discussion
Previous discussion
Another important note is that we may want to release a pycytominer version 0.1.5 prior to merging this contribution (this contribution can be pycytominer version 0.2), just to make sure pycytominer is completely up-to-date functionally, in an intermediate, but stable version.
I'll also loop in @d33bs about this decision point. Dave, does this release schedule sound like a reasonable strategy? (Beth, note that @d33bs's #203 PR is to a develop branch, but his #197 is to master.)
If the release strategy looks kosher, then we'll likely want to:
Thank you @gwaybio - sounds good to me! Small suggestion: If using 3 number versioning (v.0.1.5) it may be beneficial to stick with that convention throughout for clarity (v0.2.0 instead of v0.2).
In #160, several of us discussed a potential release strategy. I'll break out this discussion in a new issue, where we can continue a discussion
Previous discussion
Another important note is that we may want to release a pycytominer version 0.1.5 prior to merging this contribution (this contribution can be pycytominer version 0.2), just to make sure pycytominer is completely up-to-date functionally, in an intermediate, but stable version.
I'll also loop in @d33bs about this decision point. Dave, does this release schedule sound like a reasonable strategy? (Beth, note that @d33bs's #203 PR is to a develop branch, but his #197 is to master.)
If the release strategy looks kosher, then we'll likely want to:
a. And resolve Conda recipe to support optional install of cytominer-database conda-forge/pycytominer-feedstock#1
The text was updated successfully, but these errors were encountered: