-
Notifications
You must be signed in to change notification settings - Fork 1
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
Meta: v0.1.0 #1
Comments
This looks good. Obviously point that you could use individual issues and a project workflow but this will work. I'd also maybe ordering these in terms of when you will do them (i.e README updates have just happened and I assume CI is a priority) |
I'm tempted to say once currents PRs are in that should be 0.1.0 release and then move all the tooling around that here to 0.2.0 (and move that to 0.3.0) etc |
Would it be possible to include a "getting_started" vignette or readme with 0.1.0? Other than that I'm supportive! |
I want to hold the getting started vignette until we have some simulated data to fit to (#9). The readme should definitely make it though. Thoughts on including the data + vignette or bumping? |
I don't have strong opinions -- I think this depends on whether the goal of the release is to have something for you to pin to, or for others to use/follow |
Yeah exactly. I would vote go as it's nice to have something to pin to and point to say this is the initial idea but if the plan is to send it to users we should wait. |
Goal
Tracking the steps to an initial release. The goal is a minimum installable package. Useful but non-required functionality is pushed out to v0.2.0.
Features
The text was updated successfully, but these errors were encountered: