Our current ActionBar implementation will be stupid in 3.0 and up, so we'll have to drop it in favor of the native ActionBar APIs to match the rest of the OS.
Our best bet is to split things into probably four branches (dropping master) similar to the way :
2.x-dev (our current 'actionbar')
2.x-release (our current 'release' branch)
3.x-dev
3.x-release
Maybe 'native' and 'external' would be good descriptors here instead? I can't think of a good way to go on that.
From there, it's probably best to implement the new actionbar APIs and emulate the native behavior in the older version.
Our current ActionBar implementation will be stupid in 3.0 and up, so we'll have to drop it in favor of the native ActionBar APIs to match the rest of the OS.
Our best bet is to split things into probably four branches (dropping master) similar to the way :
From there, it's probably best to implement the new actionbar APIs and emulate the native behavior in the older version.