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

Minim 1.0.0 #83

Open
smizell opened this issue Sep 19, 2015 · 5 comments
Open

Minim 1.0.0 #83

smizell opened this issue Sep 19, 2015 · 5 comments

Comments

@smizell
Copy link
Contributor

smizell commented Sep 19, 2015

Per issue #81, it seems like a good idea to move forward to 1.0.0 as soon we can. I've tried to go through and put the issues under the milestone of 1.0.0 that seem to be important to complete before we say "this is stable."

In addition that, I'd be really interested in other's thoughts. Is there anything else? Should any of the issues I've added not be considered?

@pksunkara
Copy link
Contributor

I am wondering if we want to sync up with refractproject/rfcs#13

@smizell
Copy link
Contributor Author

smizell commented Sep 21, 2015

@pksunkara Do you mean move this to the RFC, or to include things from the RFC for 1.0.0?

@smizell
Copy link
Contributor Author

smizell commented Sep 21, 2015

Or timing?

@pksunkara
Copy link
Contributor

When we release refract v1, I think we should do minim v1 which fully supports refract v1. But I also doubt that we should actually do that since there can be a backward incompatible changes in minim unlike refract for further versions. A minor version change in refract change can lead to major version change in minim.

What do you think?

@smizell
Copy link
Contributor Author

smizell commented Sep 23, 2015

I like the idea of them both going to 1.0.0 at around the same time. My hope is that 1.0.0 for both of them is more so just establishing the API is now stable. I think we should try to make it where going to it is a relatively small thing.

But I also agree, I don't think we can keep the version numbers in step with each other.

kylef pushed a commit that referenced this issue Jan 9, 2018
Add headers1A property to the AST for both API Blueprint and Refract adapters
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