You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: text/0056-improved-release-cycle.md
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
- Start Date: 2015-10-02
2
+
- RFC PR: https://github.com/emberjs/rfcs/pull/56
3
+
- Ember Issue: (leave this empty)
4
+
1
5
# Refining the Release Process
2
6
3
7
Ember balances a desire for overall stability with a desire for continued improvements using a two-pronged approach:
@@ -196,4 +200,4 @@ The canary and beta cycles help to ensure that popular add-ons work by the time
196
200
197
201
That doesn't mean that add-on authors should never use private APIs: to the contrary, use of private APIs when no other choice is available helps us discover what APIs are missing.
198
202
199
-
But a major goal of the 2.x series of Ember should be to identify ways to extend the stability promises that Ember offers to application authors to add-on authors.
203
+
But a major goal of the 2.x series of Ember should be to identify ways to extend the stability promises that Ember offers to application authors to add-on authors.
0 commit comments