<br><br>On Monday, January 20, 2014, Karel Piwko <<a href="mailto:kpiwko@redhat.com">kpiwko@redhat.com</a>> 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:17:00 +0100<br>
Matthias Wessendorf <<a href="javascript:;" onclick="_e(event, 'cvml', 'matzew@apache.org')">matzew@apache.org</a>> wrote:<br>
<br>
> On Monday, January 20, 2014, Karel Piwko <<a href="javascript:;" onclick="_e(event, 'cvml', 'kpiwko@redhat.com')">kpiwko@redhat.com</a>> wrote:<br>
><br>
> > On Mon, 20 Jan 2014 12:27:22 +0100<br>
> > Matthias Wessendorf <<a href="javascript:;" onclick="_e(event, 'cvml', 'matzew@apache.org')">matzew@apache.org</a> <javascript:;>> wrote:<br>
> ><br>
> > > On Mon, Jan 20, 2014 at 12:17 PM, Karel Piwko<br>
> > > <<a href="javascript:;" onclick="_e(event, 'cvml', 'kpiwko@redhat.com')">kpiwko@redhat.com</a><javascript:;>><br>
> > wrote:<br>
> > ><br>
> > > > > +1 on postponing to a later point. If ready by April, should be fine<br>
> > as<br>
> > > > > well (my opinion). Bruno had a good point, that the postponed release<br>
> > > > > should not stop us from releasing (unstable) snapshots for testing<br>
> > > > reasons.<br>
> > > > > I like that: Release often, release early.<br>
> > > ><br>
> > > > What is actually an (unstable) snapshot? Could you shed more light on<br>
> > that?<br>
> > > ><br>
> > ><br>
> > > I'd say a regular snapshot, from master branch, released to the snapshot<br>
> > > repo<br>
> ><br>
> > That's good until another project(s) will rely on it. You update snaphot<br>
> > and<br>
> > other projects will get broken without any option to avoid that. It would<br>
> > be<br>
> > much better to make snapshots stable in time, as I described in 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 projects<br>
are released as Final is too late. I'm looking for some model in between to let<br>
us keep pace with devs.</blockquote><div><br></div><div>Well, when something is under heavy development, like ALL the sync things, it makes sense to do snapshots; when things(e.g protocol, server etc) changes, sure we will update our unit tests and adjust the clients; thats basically the development of sync;</div>
<div><br></div><div>You talking about integration tests or what? <span></span></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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 other<br>
> > and<br>
> > > > used<br>
> > > > within other projects.<br>
> > > ><br>
> > > > Karel<br>
> > > > _______________________________________________<br>
> > > > aerogear-dev mailing list<br>
> > > > <a href="javascript:;" onclick="_e(event, 'cvml', '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>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="javascript:;" onclick="_e(event, 'cvml', '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="javascript:;" onclick="_e(event, 'cvml', '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><br><br>-- <br>Sent from Gmail Mobile<br>