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

Release v0.7 #165

Open
5 of 7 tasks
jank324 opened this issue May 28, 2024 · 10 comments
Open
5 of 7 tasks

Release v0.7 #165

jank324 opened this issue May 28, 2024 · 10 comments
Labels
release For issues that rack todos for future releases

Comments

@jank324
Copy link
Member

jank324 commented May 28, 2024

Checklist for v0.7 release features

Let's discuss what features we want to have ready before releasing v0.7.

@jank324
Copy link
Member Author

jank324 commented May 28, 2024

One thought, now that we are a couple more people contributing to Cheetah, we should use this release to establish common ground on certain foundational design choices, e.g. the coordinate system. So if there is something like that you thing needs to be discussed, please bring it up here.

@cr-xu
Copy link
Member

cr-xu commented May 29, 2024

From the discussion before, the current plan is to

@jank324
Copy link
Member Author

jank324 commented Jul 10, 2024

I have some proposals on revising the plan for v0.7.0, considering that the version of Cheetah on master is by now very different from the most recent stable release you would get from PyPI ( v0.6.3 without vectorisation and such).

So I guess we could release v0.7.0 as soon as #213 is merged and #163 is finalised and merged. The only open question is if we would want to wait for #208.

@cr-xu
Copy link
Member

cr-xu commented Jul 10, 2024

I believe #164 is already fixed with #209.

@jank324
Copy link
Member Author

jank324 commented Jul 24, 2024

#227 will have to be fixed before release as well.

@jank324
Copy link
Member Author

jank324 commented Aug 26, 2024

#241 also needs fixing before this release!

@jank324
Copy link
Member Author

jank324 commented Aug 26, 2024

#246 also goes on the list.

@Hespe
Copy link
Member

Hespe commented Sep 12, 2024

#250 should probably also be addressed before the release.

@cr-xu
Copy link
Member

cr-xu commented Sep 23, 2024

I really think #208 should be merged asap as it is the most breaking change, otherwise a lot of the PRs still need to adapt to it afterwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release For issues that rack todos for future releases
Projects
None yet
Development

No branches or pull requests

3 participants