Beginning to reinvisage how bundles will be configured.
Adding an Asset bean

Bundles will deal in asset beans as this will allow us to do like: bundle.asset('myasset').before('someasset', 'anotherasset' ).after( 'jquery' ), etc.
A little error checking
Adding chainable before() and after() methods for defining asset orders
Method for adding multiple assets at once based on wildcard pattersn
Ability to pass 'match' argument to addAssets() as a closure
Refactoring the bundle manager to use a Configuration CFC file for each bundle

The CFC file must have a method called configure() that takes a Bundle object as its first argument. It can then interact with that bundle object as it sees fit
Making the sortOrder utility object work with the new method of dealing with asset bundles (we now have an asset bean, rather than plain structure
Making the includeRenderer utility object work with the new method of dealing with asset bundles (we now have an asset bean, rather than plain structure
Fixing tests that broke after we extended the Asset bean with more properties
Removing defunct references to manifest, we've thankfully ditched that concept
Refactoring the core API to use the new bundle methodology
Allowing 'media' and 'ie' restrictions to be defined when adding assets
Throwing a helpful error when bundle directory does not have a StickerBundle.cfc file