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