Skip to content
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

Move ML processes to 2.1.0 #416

Open
m-mohr opened this issue Mar 10, 2023 · 2 comments · Fixed by #417 · May be fixed by #441
Open

Move ML processes to 2.1.0 #416

m-mohr opened this issue Mar 10, 2023 · 2 comments · Fixed by #417 · May be fixed by #441
Milestone

Comments

@m-mohr
Copy link
Member

m-mohr commented Mar 10, 2023

As they are very unstable and a lot of discussions are still ongoing, I'd propose to remove the ML-related processes from the 2.0.0 release branch and keep them in a separate branch for 2.1.0.

@m-mohr m-mohr added this to the 2.0.0 milestone Mar 10, 2023
m-mohr added a commit that referenced this issue Mar 14, 2023
m-mohr added a commit that referenced this issue Mar 14, 2023
This was linked to pull requests Mar 14, 2023
m-mohr added a commit that referenced this issue Mar 14, 2023
* Remove ML processes for 2.0.0 #416
@m-mohr m-mohr modified the milestones: 2.0.0, 2.1.0 Mar 14, 2023
@soxofaan
Copy link
Member

should we also remove fit_curve (which is also some kind of ML process)?
(also see #425)

@m-mohr
Copy link
Member Author

m-mohr commented Mar 16, 2023

no, fit_curve was already included in the 1.2.0 release.

m-mohr added a commit that referenced this issue May 15, 2023
@m-mohr m-mohr linked a pull request May 15, 2023 that will close this issue
@m-mohr m-mohr linked a pull request May 15, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants