<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 10, 2015 at 5:28 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 2015-02-10, Summers Pittman wrote:<br>
> On 02/10/2015 09:35 AM, Bruno Oliveira wrote:<br>
> > Good morning, I'm doing some housekeeping on AGSEC and would like to<br>
> > know what works best for you.<br>
> ><br>
> > For the further releases and for the sake of sanity at the roadmap, I'm<br>
> > separating the security releases by component:<br>
> ><br>
> > - Crypto<br>
> > - Sync<br>
> > - OTP<br>
> > - push<br>
> > - OAuth2<br>
> > - offline<br>
> ><br>
> > They are pretty much "virtual" because it project follows its own<br>
> > release process and I just want to group by feature. For versioning what<br>
> > would be better for you:<br>
> ><br>
> > 1. Versioning from scratch which pretty much means each component starts<br>
> > with 0.0.1 and we increase accordingly with the progress.<br>
> ><br>
> > 2. Follow the Security roadmap versioning<br>
> > (<a href="https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/" target="_blank">https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/</a>). Which<br>
> > means each component starting with 1.4.0 and increasing each one<br>
> > independesing.<br>
> ><br>
> > 3. Follow each project versioning which means:<br>
> > - sync: follows the same versioning for the sync server<br>
> > - push: same versioning from the push server<br>
> > Note: the idea would fail badly for OAuth2, Crypto and OTP<br>
> ><br>
> > I'd vote for 2 to prevent confusion.<br>
> Could you give examples of what each of your suggestions would look like<br>
> in terms of the project versions(AGIOS, AGDROID, etc) and the security<br>
> version(AGSEC)? I'm not sure what the consequences of each choice are.<br>
<br>
</div></div>There are no consequences to other projects, because each project<br>
follows its own versioning and AGSEC will always respect it.<br>
<br>
So when you read at the roadmap OAuth2 1.4, it beans a group of features<br>
delivered from:<br>
<br>
- AGDROID 2.0.x<br>
- AGIOS 1.x.x<br>
<br>
The versioning on AGSEC is pretty much to keep our sanity to have an<br>
idea about which features we've been planning and when, for security.<br>
<br>
Does it make sense for you?<br></blockquote><div><br></div><div><br></div><div>yes, basically a list of epics/jiras with the (in this case) OAuth2 items, linked to their platform specific implementation JIRAs</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
<br>
> ><br>
> > --<br>
> ><br>
> > abstractj<br>
> > PGP: 0x84DC9914<br>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
><br>
> --<br>
> Summers Pittman<br>
> >>Phone:404 941 4698<br>
> >>Java is my crack.<br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
--<br>
<br>
abstractj<br>
PGP: 0x84DC9914<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div></div>