<div dir="ltr">Ok, for iOS we're going to release 1.5.0 planned early next week. We'll do ML announcements.<div>++</div><div>Corinne</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 11 March 2014 13:49, Luke Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Makes sense. For the 1.4.0 js release coming out there will be a blog post announcing it. But next time we will do the heads up on the list. It wasn't on my index card 😁<br>
<br>
Sent from my iPhone<br>
<div class="HOEnZb"><div class="h5"><br>
> On Mar 11, 2014, at 7:53 AM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> wrote:<br>
><br>
> Makes sense.<br>
><br>
> --<br>
> abstractj<br>
><br>
> On March 11, 2014 at 8:34:36 AM, Matthias Wessendorf (<a href="mailto:matzew@apache.org">matzew@apache.org</a>) wrote:<br>
>>> yeah - I agree w/ these, the main point is really that before we<br>
>> ship a particular release (regardless of the platform), the<br>
>> dev-list should be given a heads-up for testing (similar to what<br>
>> you laid out).<br>
>><br>
>> That way we don't 'silently' release a piece of software<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>
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></div></div></blockquote></div><br></div>