<br><br><div class="gmail_quote">On Mon, Feb 25, 2013 at 2:15 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@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 style="word-wrap:break-word"><br><div><div class="im"><div>On Feb 24, 2013, at 1:07 AM, Douglas Campos <<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>> wrote:</div><br><blockquote type="cite">On Fri, Feb 22, 2013 at 11:25:33AM -0600, Kris Borchers wrote:<br>
<blockquote type="cite">At the same time, I am leery of leaving it in if iOS and Android don't<br>have something similar since this feature was not thoroughly<br>discussed. I would hate to leave this in, only to have to deprecate it<br>
in a later release for something that we decide works better for all<br>libs.<br></blockquote>How do you feel about node.js stability indication on APIs? Perhaps we<br>could borrow some inspiration there (and this filter API would be<br>
experimental then)<br></blockquote><div><br></div></div>So I like this idea in theory. I have a couple of concerns.</div><div><ol><li>We're talking about a specific method here which is a pretty detailed place to mark something experimental. At the same time, I wouldn't want to mark all of DataManager as experimental just because of one method.</li>
</ol></div></div></blockquote><div><br></div><div>I agree, just that particular method :) </div><div> </div><div>2) Related to #1, we would then have to go through and give a stability rating to every method of every piece of AeroGear and maintain that for every new feature, method, etc.</div>
<div>3) We would need to document our index somewhere similar to <a href="http://nodejs.org/api/documentation.html#documentation_stability_index" target="_blank">http://nodejs.org/api/documentation.html#documentation_stability_index</a></div>
<div><br></div><div><br></div><div>that would be nice, but having a doc on that particular function/method could be fine, for now...</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div class="im"><div><br></div><blockquote type="cite"><br>-- <br>qmx<br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></div></div><br></div><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></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>