-
Notifications
You must be signed in to change notification settings - Fork 47
Prepare 2.1.0 #216
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
Prepare 2.1.0 #216
Conversation
| ccasey <ccasey@651a555e-23ca-0310-84fe-ca9f7c59d2ea> | ||
| conda-bot <[email protected]> Conda Bot <[email protected]> | ||
| conda-bot <[email protected]> conda bot <[email protected]> | ||
| dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | ||
| dmartin <dmartin@651a555e-23ca-0310-84fe-ca9f7c59d2ea> | ||
| dpeterson <dpeterson@651a555e-23ca-0310-84fe-ca9f7c59d2ea> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we add proper names/emails for ccasey, dmartin, and dpeterson?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't even find the commits they have made, honestly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see plenty of GitHub usernames throughout the conda organization, likely due to old commits. I wouldn't want to block a release because of this, but maybe some cleaning up might be in order in the future.
✂️✂️✂️ Preparing new release ✂️✂️✂️
Lots of new features, so we are creating a new minor release.