<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 20, 2014 at 2:06 PM, Karel Piwko <span dir="ltr">&lt;<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@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">On Mon, 20 Jan 2014 13:41:23 +0100<br>
<div class="im">Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org">matzew@apache.org</a>&gt; wrote:<br>
<br>
&gt; On Monday, January 20, 2014, Karel Piwko &lt;<a href="mailto:kpiwko@redhat.com">kpiwko@redhat.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; On Mon, 20 Jan 2014 13:17:00 +0100<br>
</div>&gt; &gt; Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org">matzew@apache.org</a> &lt;javascript:;&gt;&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; On Monday, January 20, 2014, Karel Piwko &lt;<a href="mailto:kpiwko@redhat.com">kpiwko@redhat.com</a>&lt;javascript:;&gt;&gt;<br>
<div class="im">&gt; &gt; wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; On Mon, 20 Jan 2014 12:27:22 +0100<br>
</div>&gt; &gt; &gt; &gt; Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org">matzew@apache.org</a> &lt;javascript:;&gt; &lt;javascript:;&gt;&gt;<br>
<div class="im">&gt; &gt; wrote:<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; On Mon, Jan 20, 2014 at 12:17 PM, Karel Piwko<br>
</div>&gt; &gt; &gt; &gt; &gt; &lt;<a href="mailto:kpiwko@redhat.com">kpiwko@redhat.com</a> &lt;javascript:;&gt;&lt;javascript:;&gt;&gt;<br>
<div><div class="h5">&gt; &gt; &gt; &gt; wrote:<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; &gt; +1 on postponing to a later point. If ready by April, should be<br>
&gt; &gt; fine<br>
&gt; &gt; &gt; &gt; as<br>
&gt; &gt; &gt; &gt; &gt; &gt; &gt; well (my opinion). Bruno had a good point, that the postponed<br>
&gt; &gt; release<br>
&gt; &gt; &gt; &gt; &gt; &gt; &gt; should not stop us from releasing (unstable) snapshots for<br>
&gt; &gt; testing<br>
&gt; &gt; &gt; &gt; &gt; &gt; reasons.<br>
&gt; &gt; &gt; &gt; &gt; &gt; &gt; I like that: Release often, release early.<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; What is actually an (unstable) snapshot? Could you shed more light<br>
&gt; &gt; on<br>
&gt; &gt; &gt; &gt; that?<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; I&#39;d say a regular snapshot, from master branch, released to the<br>
&gt; &gt; snapshot<br>
&gt; &gt; &gt; &gt; &gt; repo<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; That&#39;s good until another project(s) will rely on it. You update<br>
&gt; &gt; snaphot<br>
&gt; &gt; &gt; &gt; and<br>
&gt; &gt; &gt; &gt; other projects will get broken without any option to avoid that. It<br>
&gt; &gt; would<br>
&gt; &gt; &gt; &gt; be<br>
&gt; &gt; &gt; &gt; much better to make snapshots stable in time, as I described in<br>
&gt; &gt; previous<br>
&gt; &gt; &gt; &gt; email.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Well, this is all early and understood, not why thats a problem, when<br>
&gt; &gt; &gt; DEVELOPING something...<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; That&#39;s right. But when testing something it is a problem. We don&#39;t have a<br>
&gt; &gt; bandwidth to update tests every time something get&#39;s broken due to new<br>
&gt; &gt; SNAPSHOT being released to repository. OTOH, updating tests after all<br>
&gt; &gt; projects<br>
&gt; &gt; are released as Final is too late. I&#39;m looking for some model in between<br>
&gt; &gt; to let<br>
&gt; &gt; us keep pace with devs.<br>
&gt;<br>
&gt;<br>
&gt; Well, when something is under heavy development, like ALL the sync things,<br>
&gt; it makes sense to do snapshots; when things(e.g protocol, server etc)<br>
&gt; changes, sure we will update our unit tests and adjust the clients; thats<br>
&gt; basically the development of sync;<br>
&gt;<br>
&gt; You talking about integration tests or what?<br>
<br>
</div></div>Exactly. Integration tests, especially that ones that test more Aerogear<br>
projects combined together.<br></blockquote><div><br></div><div>well, to be honest, as long as we don&#39;t really know what the server is, how the client APIs look like (e.g 0.0.1-SNAPSHOT, 0.0.2-SNAPSHOT) it&#39;s pointless to actually do that.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; Namely, is the &quot;snapshot&quot; a set of micro/minor releases of Aerogear<br>
&gt; &gt; &gt; &gt; &gt; &gt; projects?<br>
&gt; &gt; &gt; &gt; &gt; &gt; Or do you plan to release every Aerogear project as -SNAPSHOT? Or<br>
&gt; &gt; &gt; &gt; &gt; &gt; introducing<br>
&gt; &gt; &gt; &gt; &gt; &gt; -milestone/.Mx/alpha/beta/cr/timestamp/any-qualifier-you-like into<br>
&gt; &gt; &gt; &gt; version<br>
&gt; &gt; &gt; &gt; &gt; &gt; strings?<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; I don&#39;t think 2/ option is a good idea, especially if SNAPSHOTs are<br>
&gt; &gt; &gt; &gt; &gt; &gt; released<br>
&gt; &gt; &gt; &gt; &gt; &gt; early &amp; often. That would be a maintenance/testing nightmare, if<br>
&gt; &gt; &gt; &gt; various<br>
&gt; &gt; &gt; &gt; &gt; &gt; SNAPSHOTs of the same project cannot be distinguished from each<br>
&gt; &gt; other<br>
&gt; &gt; &gt; &gt; and<br>
&gt; &gt; &gt; &gt; &gt; &gt; used<br>
&gt; &gt; &gt; &gt; &gt; &gt; within other projects.<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; Karel<br>
&gt; &gt; &gt; &gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; &gt; &gt; &gt; aerogear-dev mailing list<br>
</div>&gt; &gt; &gt; &gt; &gt; &gt; <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> &lt;javascript:;&gt; &lt;javascript:;&gt;<br>
<div class="im">&gt; &gt; &gt; &gt; &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; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; &gt; aerogear-dev mailing list<br>
</div>&gt; &gt; &gt; &gt; <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> &lt;javascript:;&gt; &lt;javascript:;&gt;<br>
<div class="HOEnZb"><div class="h5">&gt; &gt; &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; &gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &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> &lt;javascript:;&gt;<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; &gt;<br>
&gt;<br>
&gt;<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>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>