-
Notifications
You must be signed in to change notification settings - Fork 13
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
use conda-forge #148
use conda-forge #148
Conversation
It looks like the AppVeyor failure here is unrelated to this PR. |
All of these PR should have been committed to the |
Sorry for the trouble. It is hard to revert to an exception workflow when working on many other OSS projects that adhere to the standard workflow. But I'll try to remember next time 😬 BTW, maybe the "use-development-branch-as-master" workflow should be documented in the README file to help people outside of the ODM2 circle contribute to the code here. |
No worries. I should've checked.
That's a great idea. Thanks. I'll add that in somewhere. @ocefpaf The ODM2 Team has been following the Gitflow workflow. |
Maybe you should just mention that in the README. It is not widely used and more people will trip on this. |
Thank you for the article. 😄 Very useful! |
And also just one person's opinion. I disagree with the statement that it's not widely used, and so does your blogger (even though he clearly doesn't like it)! |
Indeed. That blog was just an example I sent to @lsetiawan.
It was at the time of the original post and in the web community. Since then it became obscure and the vast majority of the OSS community dropped the gitflow. However, it is important to note that the best workflow is the one you are used to 😉 ODM2 should only change from gitflow to another community standard if the group wants to reduce the learning curve for newcomers. |
@lsetiawan and @emiliom this PR makes use of the conda-forge version of the odm2 packages.