[browsermedia#416] Add browsercms to Gemfiles via :git

Confirmed that changes for browsermedia#448 allow BrowserCMS to be added to project using :git rather than released gem.

Author: peakpg

doc/release_notes.txt

@@ -18,6 +18,7 @@ Add the ability to add BrowserCMS to Rails projects.
 * [#3] Asset Pipeline: All bcms assets are now served using the assets pipeline.
 * [#443] Removed two primative javascript and stylesheets in favor of asset pipeline (where needed).
 * [#448] Mountable Engines - BrowserCMS is now a mountable engine, which should make integrating it with other projects easier.
+* [#416] BrowserCMS can be added to Gemfiles using :git or :path, which should make testing gems or projects easier.
 
 v3.3.0
 ======

upgrading_to_3_1.md

@@ -7,28 +7,27 @@ Make migrate generation use 3.1 style
 Needs
 -----
 
-* Add ticket for upgrading to Rails 3.1
+* Merge 3.1.x into project (:move_permantly)
+* Merge 3.3.x into project (misc fixes)
 * Differ `bundle install` from happening until Gemfile is updated to include bcms
 * Remove bespin
 * Improve Performance - Sitemap and serving pages is particularly slow
 ** Use Ancestry gem - It handles automatically turning models into tree via a single column. Would be very very performant in comparison to current behavior.
+* Update a few modules (like bcms_news) to test module generation
+* Test this on a production enviroment prior to releasing (things like assets might be wonky)
 
 Wants (Taking advantage of 3.1)
 -----
 
+* Internal CMS layouts (like _head.html.erb) do not take advantage of the asset pipeline to join all css or js files (most are compiled into cms/application.css though)
 * Improve generators for assets from engines (Review http://bibwild.wordpress.com/2011/09/20/design-for-including-rails-engine-assets-into-pipeline-manifest/)
 * Remove the styled_file_field (no longer maintained)
-* [#416] Make bcms includable as part of a Gemfile using git
 * Migrations have a single 'def change' method now, rather than self.up and self.down
 * Themes can be packaged as assets as well (I think?). Rework bluesteel so its part of the asset pipeline.
 * Run in production mode locally (for better error testing). Try POW to see if that adds subdomains easily.
 * Design how a portlet can include a single jquery based library by just declaring it in the render.html.erb.
 ** eg. auto_discovery_link_tag -> Does not get included in the head
 * Add better messaging for `browsercms demo [NAME]`
-
-
-Ideas
------
 * Allow for multiple view templates for blocks.
 * Look at Papertrail and see how they structure versions. Their API seems every simple for single blocks.