<div>
Yep, as I said yesterday at our meeting ;)</div>
<div><div><br></div><div><br></div><div><div>-- </div><div>"The measure of a man is what he does with power" - Plato</div><div>-</div><div>@abstractj</div><div>-</div><div>Volenti Nihil Difficile</div></div></div>
<p style="color: #A0A0A8;">On Wednesday, September 19, 2012 at 11:41 AM, Matthias Wessendorf wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Looks like the Security Document should be updated too?</div><div><br></div><div><a href="http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearSecurity/">http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearSecurity/</a></div><div><br></div><div>(talks about beta)</div><div><br></div><div>On Wed, Sep 19, 2012 at 4:35 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><blockquote type="cite"><div><div>Glad, I asked :)</div><div><br></div><div>On Wed, Sep 19, 2012 at 4:27 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:</div><blockquote type="cite"><div><div>Android should not have a beta. I had a beta originally but was told to change to milestones in JS.</div><div><br></div><div>On Sep 19, 2012, at 8:49 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><div><br></div><blockquote type="cite"><div><div>Hi,</div><div><br></div><div>I am looking at polishing the iOS roadmap and did take a look at the</div><div>roadmaps for Android and JS (see [1] and [2]).</div><div><br></div><div>Personally I think they are kinda confusing, since they talk about</div><div>different releases...</div><div><br></div><div>The JS lib talks about:</div><div>- 1.0.0.Alpha1 (and says release with AeroGear 1.0.0M5)</div><div>- 1.0.0.M1 (and says release with AeroGear 1.0.0M6)</div><div>- 1.0.0.M2 (and says release with AeroGear 1.0.0M7)</div><div>- 1.0.0.CR1 (and says release with AeroGear 1.0.0CR)</div><div>- 1.0.0.Final (and says release with AeroGear 1.0.0Final)</div><div><br></div><div>While the Android lib talks about:</div><div>- 1.0.0.Alpha1 (and says release with AeroGear 1.0.0M6)</div><div>- 1.0.0.Alpha2</div><div>- 1.0.0.Beta</div><div>- 1.0.0.Final</div><div><br></div><div>Not sure if it's helpful if the different libs use different terms</div><div>(e.g. Alpha vs. milestone vs. beta)...</div><div><br></div><div>What's clear (if I get it right) are the 'raw' release dates for the</div><div>'umbrella AeroGear' releases:</div><div>- 1.0.0M6 ==> ~ mid Oct 2012</div><div>- 1.0.0M7 ==> ~ mid Dec 2012</div><div>- 1.0.0CR ==> ~ mid Feb 2013</div><div>- 1.0.0Final ==> ~ mid Apr 2013</div><div>(basically, every 8 weeks, right ?)</div><div><br></div><div>What's also clear (IMO) is that these individual components do NOT</div><div>need to match the exact 'release label' of the 'umbrella' AeroGear...</div><div>But... not sure if they should at least kinda match a common</div><div>'semantic' (e.g. Milestone, Beta etc). I tend to say yes here...</div><div><br></div><div>Background:</div><div>I want to know the 'labeling' because I am TRYING :) to identify</div><div>reasonable pieces for the iOS library, to be released along the</div><div>'umbrella' AeroGear release, but got confused since Android has a beta</div><div>and JS has 'only' milestones :)</div><div><br></div><div>Any thoughts?</div><div><br></div><div>-Matthias</div><div><br></div><div>[1] <a href="http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearAndroid/">http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearAndroid/</a></div><div>[2] <a href="http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearJS/">http://staging-aerogear.rhcloud.com/docs/planning/1.0.0/AeroGearJS/</a></div><div><br></div><div>--</div><div>Matthias Wessendorf</div><div><br></div><div>blog: <a href="http://matthiaswessendorf.wordpress.com">http://matthiaswessendorf.wordpress.com</a>/</div><div>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a></div><div>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a></div><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote><div><br></div><div><br></div><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote><div><br></div><div><br></div><div><br></div><div>--</div><div>Matthias Wessendorf</div><div><br></div><div>blog: <a href="http://matthiaswessendorf.wordpress.com">http://matthiaswessendorf.wordpress.com</a>/</div><div>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a></div><div>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a></div></div></blockquote><div><br></div><div><br></div><div><br></div><div>-- </div><div>Matthias Wessendorf</div><div><br></div><div>blog: <a href="http://matthiaswessendorf.wordpress.com">http://matthiaswessendorf.wordpress.com</a>/</div><div>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a></div><div>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a></div><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>