[aerogear-dev] [rfc] AeroGear 2.x RoadMap

[Karel Piwko]

On Tue, 14 May 2013 16:49:03 -0300
Douglas Campos <qmx at qmx.me> wrote:

> This is the *tentative* proposed[1] RoadMap for AeroGear 2.x
> 
> * AeroGear (~2wks) (Late May)
>     - point releases across the sub-projects
> 
> * AeroGear 1.1.0 (~6wks) (Mid July)
> 	
> 	This is a lot for 4 weeks
> 	
> 	Epics:
> 	-	CI across all projects
This is interesting. Is that about using Travis, Cloudbees, Red Hat Jenkins
instance with jobs managed by QE or something else?

> 		- Emailing, tweeting, some way to consume (aerogear-build
> list)?
+1 to special list, much easier to consume results this way
> 		- Project site with links, details, and if possible current
> build status
> 			- Similar to what is showing in the repo
> 	- Release Standards
> 	- Specification standards
> 	- Move aerogear.org / staging.aerogear.org out of jborgs
> 	- Site design updates
> 	- GitHub clean up
> 		- Repo review, and README standards   
> 	- Getting starting experience
> 		- Check docs, examples
> 
> * AeroGear 1.2.0 (~+6 wks) (Late August)
> 	
> 	Epics:
> 	-	Unified push server
> 		-	Server, client, and basic admin UI
> 		-	Extra getting started guides, and polished example
> 		-	Polished OpenShift experience
> 
> * AeroGear 1.3.0 (~+6wks) (Mid October)
> 	
> 	Epics:
> 	-	Security
> 		-	Define it clearly
> 		-	encrypted local storage
> 	- Integration functionality
> 		-	Simple integration options (basic WS client work)
> 		- Mostly server-side work
> 
> * \<holidays>
> 
> * AeroGear 1.4.0 (~+6wks) (Early December)(Late January)
> 	
> 	Epics
> 	-	Offline/sync
> 
> * AeroGear 2.0.0 (~+6wks) (Late January)
> 	
>     \<insert your favorite beverage here>!
> 
> 
> Your comments are more than welcome! nothing is set on stone (yet :P).
> 
> [1]:https://github.com/aerogear/aerogear.org/pull/60
>