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

New release #769

Open
KristofferC opened this issue Nov 3, 2021 · 4 comments
Open

New release #769

KristofferC opened this issue Nov 3, 2021 · 4 comments

Comments

@KristofferC
Copy link
Contributor

#759 would be good to have in a release.

@oxinabox
Copy link
Member

oxinabox commented Nov 4, 2021

The plan is to not make any 0.19 release until we are ready to make a 1.0 release immediately after.
See #479

If someone wants to do the work to backpoint #759 to the 0.18 branch that is fine (assuming non-breaking)

@KristofferC
Copy link
Contributor Author

Looking at how long ago that issue was opened that didn't seem like too great of a plan. In the meantime improvements just accumulate on the master branch because it has been decided it will not get released?

@oxinabox
Copy link
Member

oxinabox commented Nov 5, 2021

Looking at how long ago that issue was opened that didn't seem like too great of a plan.

It's the only plan, I have.
Minimize gaining new features (especially new datastructures) that are unrelated to hitting 1.0, until we hit stability.
Since gaining new features takes that goal further from completion.
if you have a better plan that will let us get rid of all the code that follows julia 0.3 conventions, I am keen to hear it.

Breaking changes are too distruptive for this package.
But they are needed for a lot of the changes that are needed.
So we just want to get them all done.

In the meantime improvements just accumulate on the master branch because it has been decided it will not get released?

Or they get backported.
We have done a fair few backport releases.


TBH I don't have enough time to get us to 1.0 any time soon.
I barely have the time to triage bug reports and review the PRs as it is.
If anyone has time to dedicate to getting us to 1.0 it would be awesome.
If you, or someone else I trust like I trust you, want to take on the ownership of the package and advancing it's vision, I would be quite down to hand-off responsibility.
(It is, as you know, a thankless task)

@MartinKocour
Copy link

Any update about #759 ?

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

No branches or pull requests

3 participants