[aerogear-dev] AGSEC components and versioning

[Summers Pittman]

On 02/10/2015 09:35 AM, Bruno Oliveira wrote:
> Good morning, I'm doing some housekeeping on AGSEC and would like to
> know what works best for you.
>
> For the further releases and for the sake of sanity at the roadmap, I'm
> separating the security releases by component:
>
> - Crypto
> - Sync
> - OTP
> - push
> - OAuth2
> - offline
>
> They are pretty much "virtual" because it project follows its own
> release process and I just want to group by feature. For versioning what
> would be better for you:
>
> 1. Versioning from scratch which pretty much means each component starts
>    with 0.0.1 and we increase accordingly with the progress.
>
> 2. Follow the Security roadmap versioning
>    (https://aerogear.org/docs/planning/roadmaps/AeroGearSecurity/). Which
>    means each component starting with 1.4.0 and increasing each one
>    independesing.
>
> 3. Follow each project versioning which means:
>    - sync: follows the same versioning for the sync server
>    - push: same versioning from the push server
>    Note: the idea would fail badly for OAuth2, Crypto and OTP
>
> I'd vote for 2 to prevent confusion.
Could you give examples of what each of your suggestions would look like 
in terms of the project versions(AGIOS, AGDROID, etc) and the security 
version(AGSEC)?  I'm not sure what the consequences of each choice are.
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


-- 
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.