<div dir="ltr"><div class="gmail_extra">Hello there!</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 18, 2014 at 9:25 PM, Bruno Oliveira <span dir="ltr">&lt;<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>&gt;</span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Good morning team,<br>
<br>
After some discussion at this PR<br>
<a href="https://github.com/aerogear/aerogear-android-cookbook/pull/22" target="_blank">https://github.com/aerogear/aerogear-android-cookbook/pull/22</a>. I was<br>
wondering if would be nice on having the zip files with the latest<br>
cookbook stable version. Like we do for UPS<br>
<a href="https://github.com/aerogear/aerogear-unifiedpush-server/releases" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server/releases</a></blockquote><div><br></div><div>I think it would be nice if the cookbook usage experience for our users is as simple as possible:</div><div>- clone master</div><div>- build the app</div><div>- deploy</div><div>- profit </div><div><br></div><div>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.</div><div><br></div><div><br></div><div>+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.</div><div><br></div><div>-Matthias</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
<br>
This is not specific for Android, I saw that some projects are already<br>
doing it like AGJS, we just need to keep the pace.<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>
</blockquote></div><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>