[aerogear-dev] Roadmaps / release dates

Matthias Wessendorf matzew at apache.org
Wed Sep 19 10:35:11 EDT 2012


Glad, I asked :)

On Wed, Sep 19, 2012 at 4:27 PM, Kris Borchers <kris at redhat.com> wrote:
> Android should not have a beta. I had a beta originally but was told to change to milestones in JS.
>
> On Sep 19, 2012, at 8:49 AM, Matthias Wessendorf <matzew at apache.org> 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)...
>>
>> 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 ?)
>>
>> 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...
>>
>> 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
>
>
> _______________________________________________
> 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


More information about the aerogear-dev mailing list