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.

Sign up for GitHub

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

Jump to bottom

stability #14

Open
jonathanong opened this issue Sep 4, 2014 · 5 comments
Open

stability #14

jonathanong opened this issue Sep 4, 2014 · 5 comments

Comments

@jonathanong
Copy link
Contributor

stable, unstable, and experimental, defaulting to stable if v1+.

it'll just be a warning to users on how to use the module. ex. templation would be experimental but it's already v1 because i want to cohere to semver anyways. cookie and cookies would be unstable because we plan to drastically rewrite and refactor it.
@rlidwka
Copy link
Member

rlidwka commented Sep 4, 2014

Like node.js stability index? Some people tried to apply the same to modules (https://github.com/dominictarr/stability).

@yoshuawuyts
Copy link

This is a little outdated, but might still be useful -- https://github.com/hughsk/stability-badges

@Fishrock123
Copy link
Member

API Frozen and Locked are nonsense, let's not go that way at all, please.

@jonathanong
Copy link
Contributor Author

yeah i don't think a module should ever be frozen or locked. maybe deprecated, though at that point you shouldn't even list it on the board

@dougwilson
Copy link
Member

yea, "frozen" or "locked" is another way to tell people "i don't give a f about this anymore; it's dead and not changing"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@dougwilson @jonathanong @rlidwka @Fishrock123 @yoshuawuyts