[aerogear-dev] Update JS Roadmap

[Kris Borchers]

OK everyone,

I have made updates to the roadmap based on feedback. I am including the full updated roadmap below for comments. The change highlights include:
Removed OData adapter for Pipeline until further research can be done
Moved all target timeframes to mid-month to allow for proper freezes before umbrella project releases.
Broke showcase app across multiple milestones since it will be an ongoing project
Moved Data Sync to 1.3.0 to allow better work division with Offline which remains in 1.4.0


# AeroGear.js Roadmap

## 1.0.x Release(s)
* **Bug Fixes and Minor Feature Additions**
* **Dates**
	* Released as needed
	* If not critical, can be wrapped into a 1.x release

## 1.1.0 (Mid June)
### New Features
* **OTP**
	* Sync with Bruno's works and help where needed
* **Notifier**
	* Used for background communication in applications
	* Adapters
		* SockJS or some other fallback strategy
		* More? (STOMP and other protocols to "unify" APIs)
			* Can be moved to future releases

## 1.2.0 (Mid August)
### New Features
* **SimplePush**
	* Base on Mozilla's SimplePush Protocol Specification
	* WebSocket/SockJS via Notifier
* **Unified Push Client**
	* Separate module for app registration/unregistration with unified push server
* **Showcase App**
	* First version featuring all features from library up to this point

### New Adapters
* **DataManager**
	* IndexedDB/WebSQL Adapter
		* Feature detection to determine which is available
		* IE9 supports neither so need to also be able to fall back to localStorage but use same API
		* Probably should investigate PouchDB's implementation
* **Auth**
	* OTP
		* Adapter or standalone
	* OAuth2 Adapter
		* Customizable Provider

## 1.3.0 (Mid October)
### New Features
* **Pipeline**
	* Multi-part Uploads
* **DataManager**
	* Add encryption to sessionLocal adapter
* **Data Sync**
	* Utility for keeping data in DataManager synchronized with a persistent server side store
	* Possibly use Notifier for communication / data transfer
* **Showcase App**
	* Add latest library features

## 1.4.0 (Mid January)
### New Features
* **Offline**
	* Support for using apps offline and detecting status
	* Simplified App Cache API
	* Scaffolding for proper App Cache setup
	* Use DataSync when returning to online status
* **Showcase App**
	* Add latest library features


## 2.0.0 Release
* Tie up any loose ends
  
## 2.x Release(s)
* **Social**
	* Auth
		* Login via Facebook, G+, Twitter?
		* AeroGear.Auth adapter or separate?
	* Common API
		* Posting, Profile Info, Friend List, etc.



On May 20, 2013, at 3:55 PM, Kris Borchers <kris at redhat.com> wrote:

> 
> On May 16, 2013, at 7:33 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
>> 
>> 
>> 
>> On Fri, May 17, 2013 at 12:23 AM, Douglas Campos <qmx at qmx.me> wrote:
>> On Thu, May 16, 2013 at 04:30:54PM -0500, Kris Borchers wrote:
>> > > ## 1.1.0 (Late June)
>> ...
>> > > ### New Adapters
>> > > * **Pipeline**
>> > >     * OData Adapter - [http://www.odata.org/](http://www.odata.org/)
>> > >             * Investigate continued support / viability (Netflix dropping?)
>> mixed feelings about this one - both time-wise and viability wise.
>> 
>> same here - really needed ?
> 
> I am leaning toward removing this. Luke and Sebastien, did either of you get a chance to look into this more? Maybe we put it on the back burner and we can add it back to the roadmap further down the road if we decide it is still something worth pursuing?
> 
>> 
>> 
>> 
>> 
>>  
>> 
>> > > ## 1.2.0 (Late August)
>> On the main roadmap we're releasing the umbrella project on Late august,
>> so ideally this would need to come Mid-August so that we can have a
>> decent freeze window
>> 
>> > > ## 1.4.0 (Late January)
>> This timing seems a little bit off from the main roadmap - and the scope
>> is pretty big - wouldn't it be a good idea to try harder to split data
>> sync and offline? (I know this is hard)
>> > > ### New Features
>> > > * **Data Sync**
>> > >     * Utility for keeping data in DataManager synchronized with a persistent server side store
>> > >     * Possibly use Notifier for communication / data transfer
>> > > * **Offline**
>> > >     * Support for using apps offline and detecting status
>> > >     * Simplified App Cache API
>> > >     * Scaffolding for proper App Cache setup
>> do this exists in real life? ;)
>> > >     * Use DataSync when returning to online status
>> 
>> 
>> --
>> qmx
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> 
>> 
>> -- 
>> Matthias Wessendorf 
>> 
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130520/d6b953ee/attachment-0001.html