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

v1.0.0 #335

Closed
svozza opened this issue Feb 14, 2017 · 7 comments
Closed

v1.0.0 #335

svozza opened this issue Feb 14, 2017 · 7 comments

Comments

@svozza
Copy link
Member

svozza commented Feb 14, 2017

Now that 0.12 has been released, is it time to formulate a strategy for how we proceed from here? I think it would be great to get a stable version out as soon as is practicable. One place I think we're deficient in is changing the properties in StrMaps, i.e., functions such as assoc, evolve etc. I'm presuming the preferred solution here is lenses and we have an issue for it already but what else needs to be added (or removed) before we're happy to cut 1.0.0?

@davidchambers
Copy link
Member

These are the changes I'd like to see before v1.0.0:

Useful functions such as assoc can easily be added in minor releases post v1.0.0. v1.0.0 needn't be "complete", but it would be nice for it to at least be clear about how the various Sanctuary projects fit together.

@svozza
Copy link
Member Author

svozza commented Feb 14, 2017

Good point regarding assoc and friends. My worry about the first two points is that it's mostly out of our hands, we're basically waiting on the outcome of an issue that's been open for months:

fantasyland/fantasy-maybes#8

I hope we're not in danger of falling into to the analysis paralysis that seems to have gripped Ramda.

@davidchambers
Copy link
Member

My worry about the first two points is that it's mostly out of our hands

I'm not convinced that moving these projects to the @fantasyland account is the right move, for reasons I will explain (at some point) in fantasyland/fantasy-maybes#8. I think we should go ahead and release sanctuary-maybe and sanctuary-either, then decide whether to move the projects. This way we're in control of our own destiny.

I hope we're not in danger of falling into to the analysis paralysis that seems to have gripped Ramda.

I don't think so. Ramda's governance is too democratic, in my view. I've encouraged Scott to adopt the role of benevolent dictator, but he's unwilling to do so. It's difficult for Ramda to move forward when prominent contributors have conflicting visions of Ramda's future, and significant changes are usually only made unanimously.

@svozza
Copy link
Member Author

svozza commented Feb 14, 2017

Ok. That's good to know, I've been holding off on doing any work on splitting out Either and Maybe because I thought we needed to wait for a decision on moving them; the analysis paralysis I was referring to was on that end rather than here because I figured there would be a lot of conflicting opinions on such a move.

@svozza
Copy link
Member Author

svozza commented Feb 15, 2017

Are the Maybe utility functions going to move to the new repo or is it literally just the data type?

@davidchambers
Copy link
Member

Are the Maybe utility functions going to move to the new repo or is it literally just the data type?

Just the data type. By keeping the project lean we'll be more likely to encourage others to use it rather than write competing implementations.

@davidchambers
Copy link
Member

Sanctuary now includes everything I hoped to include in v1.0.0. There will not be a v0.16.0. ;)

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

2 participants