-> v1.1.0

CHANGELOG.md

@@ -1,4 +1,8 @@
-## v1.0.10 (07/24/2013)
+## v1.1.0 (07/26/2013)
+
+##api changes
+* new <Component> (not recommended) no longer auto-calls initialize
+(use <Component>.attachTo)
 
 ###features
 * core component behavior now in base.js mixin/module
@@ -9,6 +13,14 @@
 * update bower resources to match current bower naming scheme
 * tools/debug.js -> lib/debug.js
 
+## v1.0.11 (07/26/2013)
+
+* rollback 1.0.10 due to API changes
+
+## v1.0.10 (07/24/2013)
+
+* becomes v1.1.0 due to API changes
+
 ## v1.0.9 (05/13/2013)
 
 ###features

bower.json

@@ -2,7 +2,7 @@
   "name": "flight",
   "description": "Clientside component infrastructure",
   "main": "lib/index.js",
-  "version": "1.0.10",
+  "version": "1.1.0",
   "ignore": [
     "tools/standalone",
     "test",

doc/base_api.md

@@ -56,11 +56,9 @@ this.selectMenuItem = function(e) {
 
 ## this.initialize()
 
-This is an empty method attached to the prototype of every Component and Mixin.
-It can be used to perform an initial setup routine when a component instance is
-created.
+This method is attached to the prototype of every Component and called when a component instance is created.
 
-The method is augmented by supplying a function as an argument to the `after`
+The method is typically augmented by supplying a function as an argument to the `after`
 method (see the [advice API](advice_api.md) for more information). This is a
 good place to set up event listeners that bind to callbacks.
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "flight",
-  "version": "1.0.10",
+  "version": "1.1.0",
   "devDependencies": {
     "karma": "~0.8.5",
     "loadbuilder": ">=0.4.2",