<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 29, 2014 at 6:00 PM, Lucas 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"><div class="im"><br>
On Jan 29, 2014, at 11:57 AM, Jay Balunas <<a href="mailto:jbalunas@redhat.com">jbalunas@redhat.com</a>> wrote:<br>
<br>
> Finally got a chance to read through the whole sync thread :-)<br>
><br>
> I'm a big fan keeping it simple, especially for initial releases. So limiting scope of our initial offering will be important imo.<br>
><br>
> I really like the idea of defining the data model, protocol, client contract, etc... separate from a specific implementation. As several have said, those are impl. details that we can change as needed. For example Push - I like the idea of using it for notification of updates (optional, with fallback, & not required), but it should not be a 1.0 priority imo. It should also be something that requires no (or minimal) updates from the app developer when we implement it. At the end of the day it is just another way to let the app know something has changed :-)<br>
><br>
</div>> As for versioning, I'm concerned over having M1, M2, etc.... What do you think of sticking with semver 0.1, 0.2, etc…?<br>
<br>
+1 to semver<br></blockquote><div><br></div><div>+1</div><div><br></div><div><br></div></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>