Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

remove "unstable" messaging #112

Merged
merged 1 commit into from
Jan 29, 2015
Merged

Conversation

Fishrock123
Copy link
Contributor

The word unstable was confusing in meaning and intent. This is arguably the most stable node release ever.

Fixes #108

@Fishrock123
Copy link
Contributor Author

@iojs/website we require signoffs now too, right? Anyone wana +1 this quick?

@indexzero
Copy link
Contributor

Thus +1ed. We so stable.

The word unstable was confusing in meaning and intent.

Fixes: #108
PR-URL: #112
@Fishrock123 Fishrock123 force-pushed the most-stable-node-release-yet branch from 930d78d to cc7b652 Compare January 29, 2015 23:25
@Fishrock123 Fishrock123 merged commit cc7b652 into master Jan 29, 2015
@Fishrock123 Fishrock123 deleted the most-stable-node-release-yet branch January 29, 2015 23:29
Fishrock123 added a commit that referenced this pull request Feb 8, 2015
The word unstable was confusing in meaning and intent.

Fixes: #108
PR-URL: #112
timaschew pushed a commit to timaschew/website that referenced this pull request Feb 13, 2015
The word unstable was confusing in meaning and intent.

Fixes: nodejs#108
PR-URL: nodejs#112
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A new way of describing "stability"
2 participants