-
Notifications
You must be signed in to change notification settings - Fork 884
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
Add looking glass launch instructions #2461
Conversation
release.md
Outdated
@@ -8,7 +8,7 @@ Before starting the release process, verify the following: | |||
- [All Github Actions Tests are green on main](https://github.com/alteryx/featuretools/actions?query=branch%3Amain). | |||
- EvalML Tests are green with Featuretools main | |||
- [![Unit Tests - EvalML with Featuretools main branch](https://github.com/alteryx/evalml/actions/workflows/unit_tests_with_featuretools_main_branch.yaml/badge.svg?branch=main)](https://github.com/alteryx/evalml/actions/workflows/unit_tests_with_featuretools_main_branch.yaml) | |||
- The latest Looking Glass performance tests runs should not show any significant performance regressions. If performance regressions have been identified, review the results with the development team to decide on the proper course of action before proceeding with the release. | |||
- Looking Glass performance tests runs should not show any significant performance regressions when comparing the last commit on `main` with the previous release of Featuretools. See below for instructions on manually launching the performance tests runs. If performance regressions have been identified, review the results with the development team to decide on the proper course of action before proceeding with the release. |
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.
Let's be more explicit here. The person releasing has to kickoff the performance tests, and look at the results.
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 worded it this way because this is in a list of things to verify, not a list of actions for the person releasing to do. Do you think the action required will be clear enough if we move the detailed instructions to Step 1 in the release process?
release.md
Outdated
@@ -123,3 +123,17 @@ Per the instructions [here](https://conda-forge.org/docs/maintainer/updating_pkg | |||
|
|||
2. A PR will be auto-created on the repo, and will need to be merged by an existing maintainer. | |||
3. The new user will need to **check their email for an invite link to click**, which should be https://github.com/conda-forge | |||
|
|||
## Manually launching Looking Glass performance runs |
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.
Let's move this up, and make it one of the first steps to releasing.
Co-authored-by: Gaurav Sheni <gvsheni@gmail.com>
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.
overall looks good. just 1 comment
Co-authored-by: Gaurav Sheni <gvsheni@gmail.com>
Codecov Report
@@ Coverage Diff @@
## main #2461 +/- ##
=======================================
Coverage 99.41% 99.41%
=======================================
Files 343 343
Lines 21056 21056
=======================================
Hits 20932 20932
Misses 124 124 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Update
release.md
to include instructions on how to manually launch Looking Glass performance test runs.