Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add release instruction #58

Merged
merged 2 commits into from
Mar 22, 2023
Merged

Add release instruction #58

merged 2 commits into from
Mar 22, 2023

Conversation

yinweisu
Copy link

Issue #, if available:

Description of changes:

  • Added release instruction based on AG release instruction.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@github-actions
Copy link

Job PR-58-5d95bba is done.
Docs are uploaded to https://d12sc05jpx1wj5.cloudfront.net/PR-58/5d95bba/index.html


* Check all dependency version ranges.
* Ensure all dependencies are not capped by major version, unless the reason is documented inline.
* Example of major version cap: `scikit-learn<2`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In quick reading this looks like an example how to do it. Maybe emphasize avoiding this? Examples usually read as instructions. (also see other places where examples are non-prescriptive).

* Ensure all dependencies are not capped by major version, unless the reason is documented inline.
  * ❎ Avoid - major version cap: `scikit-learn<2`

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good suggestion! Though we might want to do the same to our release instruction in our main repo, as this is just copied from there :)

* Example: `scikit-learn==1.1.3`. This is very fragile and overly strict.
* Ensure all dependencies are capped by minor version and not micro version unless the reason is documented inline.
* Minor version capping would be `<x.y`. Micro version capping would be `<x.y.z`.
* Avoid capping to `<x.y.0`, instead do the cleaner identical cap: `<x.y`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe split:

* ❎ Avoid: capping to `<x.y.0`
* ✅ Do: `<x.y`.

Comment on lines 16 to 17
* Example: `scikit-learn<1.2` is not reasonable because it is almost certain that `scikit-learn==0.0.1` is not supported.
* A better range: `scikit-learn>=1.0,<1.2`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

* ❎ Avoid: `scikit-learn<1.2` is not reasonable because it is almost certain that `scikit-learn==0.0.1` is not supported.
* ✅ A better range: `scikit-learn>=1.0,<1.2`

@yinweisu yinweisu merged commit 3a8ed41 into autogluon:master Mar 22, 2023
@github-actions
Copy link

Job PR-58-02e228a is done.
Docs are uploaded to https://d12sc05jpx1wj5.cloudfront.net/PR-58/02e228a/index.html

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants