<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 5, 2015 at 3:11 PM, Lucas Holmquist <span dir="ltr">&lt;<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">this sounds reasonable.<br>
<br>
<br>
Would we go back and rename previous AGPUSH releases to ups-* and also recreate the current old sps releases in AGPUSH?<br></blockquote><div><br></div><div>yes, that&#39;s a good idea.</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>
&gt; On Jan 5, 2015, at 6:53 AM, Bruno Oliveira &lt;<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>&gt; wrote:<br>
&gt;<br>
&gt; I think makes sense having all of them under AGPUSH and creating<br>
&gt; components: ups, sps and wps and manage it with the release field.<br>
&gt;<br>
&gt; +1<br>
&gt;<br>
&gt; On 2015-01-05, Matthias Wessendorf wrote:<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; right now we have three different types of &#39;push servers&#39;:<br>
&gt;&gt; * UPS<br>
&gt;&gt; * SimplePush<br>
&gt;&gt; * WebPush Server<br>
&gt;&gt;<br>
&gt;&gt; The first two ones each have their own JIRA, but I was wondering if we use<br>
&gt;&gt; the AGPUSH jira for all three.<br>
&gt;&gt;<br>
&gt;&gt; To manage releases and bugs, we will go with different/more components, and<br>
&gt;&gt; for the releases, we could do what we do successfully on our Cordova<br>
&gt;&gt; project. We can, in JIRA, have releases like:<br>
&gt;&gt;<br>
&gt;&gt; ups-1.3.0<br>
&gt;&gt; sps-1.0.0<br>
&gt;&gt; wps-0.2.0<br>
&gt;&gt;<br>
&gt;&gt; That way would have all push (server) bits on the same JIRA and<br>
&gt;&gt; differentiation is simply done using components and versions as discussed<br>
&gt;&gt; above.<br>
&gt;&gt;<br>
&gt;&gt; Any thoughts ?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Matthias Wessendorf<br>
&gt;&gt;<br>
&gt;&gt; blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
&gt;&gt; sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
&gt;&gt; twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; aerogear-dev mailing list<br>
&gt;&gt; <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
&gt;&gt; <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt; abstractj<br>
&gt; PGP: 0x84DC9914<br>
&gt; _______________________________________________<br>
&gt; aerogear-dev mailing list<br>
&gt; <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
&gt; <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>
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>