[aerogear-dev] Roadmaps / release dates

[Jay Balunas]

On Sep 19, 2012, at 9:49 AM, Matthias Wessendorf wrote:

> Hi,
> 
> I am looking at polishing the iOS roadmap and did take a look at the
> roadmaps for Android and JS (see [1] and [2]).
> 
> Personally I think they are kinda confusing, since they talk about
> different releases...
> 
> The JS lib talks about:
> - 1.0.0.Alpha1 (and says release with AeroGear 1.0.0M5)
> - 1.0.0.M1 (and says release with AeroGear 1.0.0M6)
> - 1.0.0.M2 (and says release with AeroGear 1.0.0M7)
> - 1.0.0.CR1 (and says release with AeroGear 1.0.0CR)
> - 1.0.0.Final (and says release with AeroGear 1.0.0Final)
> 
> While the Android lib talks about:
> - 1.0.0.Alpha1 (and says release with AeroGear 1.0.0M6)
> - 1.0.0.Alpha2
> - 1.0.0.Beta
> - 1.0.0.Final
> 
> Not sure if it's helpful if the different libs use different terms
> (e.g. Alpha vs. milestone vs. beta)...

* All of the sub-projects should follow Alpha, Milestone, CR, Final release naming

> 
> What's clear (if I get it right) are the 'raw' release dates for the
> 'umbrella AeroGear' releases:
> - 1.0.0M6    ==> ~ mid Oct 2012
> - 1.0.0M7    ==> ~ mid Dec 2012
> - 1.0.0CR    ==> ~ mid Feb 2013
> - 1.0.0Final ==> ~ mid Apr 2013
> (basically, every 8 weeks, right ?)

I would like to plan for an earlier release in the new year.  Also the time from the last milestone to the CRs, and to final is not a full 8 weeks, these should be more rapid turn around.

- 1.0.0M6    ==> ~ mid Oct 2012
- 1.0.0M7    ==> ~ mid Dec 2012
- 1.0.0CR1    ==> ~ mid Jan 2013
- 1.0.0CR2/Final ==>  ~ late Jan 2013 (CR2 if needed)
- 1.0.0.Final ==> ~ early Feb 2013 (if needed)

PS: I agree we need to get this written down somewhere...

> 
> What's also clear (IMO) is that these individual components do NOT
> need to match the exact 'release label' of the 'umbrella' AeroGear...
> But... not sure if they should at least kinda match a common
> 'semantic' (e.g. Milestone, Beta etc). I tend to say yes here...


* They do not need to have the same version as the umbrella release

* They do need to plan to converge for AeroGear 1.0.0.Final

> 
> Background:
> I want to know the 'labeling' because I am TRYING :) to identify
> reasonable pieces for the iOS library, to be released along the
> 'umbrella' AeroGear release, but got confused since Android has a beta
> and JS has 'only' milestones :)
> 
> Any thoughts?
> 
> -Matthias
> 
> [1] http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearAndroid/
> [2] http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearJS/
> 
> -- 
> 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