[aerogear-dev] Cookbooks stable versions

[Matthias Wessendorf]

Hello there!

On Thu, Dec 18, 2014 at 9:25 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
>
> Good morning team,
>
> After some discussion at this PR
> https://github.com/aerogear/aerogear-android-cookbook/pull/22. I was
> wondering if would be nice on having the zip files with the latest
> cookbook stable version. Like we do for UPS
> https://github.com/aerogear/aerogear-unifiedpush-server/releases


I think it would be nice if the cookbook usage experience for our users is
as simple as possible:
- clone master
- build the app
- deploy
- profit

If our users would have to build a few dependency in order to get the
cookbook demo(s) up and running, I am not sure if the experience is that
smooth.


+1 on creating tags/releases for the cookbooks. This could be done when the
cookbook is upgraded to a new version of our libraries. Another benefit
with creating these tags/releases is that this gives us a history(or list)
of demos that also show how to use slightly older versions (e.g. from last
year), instead of just the latest greatest.

-Matthias



>
>
> This is not specific for Android, I saw that some projects are already
> doing it like AGJS, we just need to keep the pace.
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141218/42dd7a0c/attachment.html