<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 24, 2013, at 1:07 AM, Douglas Campos <<a href="mailto:qmx@qmx.me">qmx@qmx.me</a>> wrote:</div><br class="Apple-interchange-newline"><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>So I like this idea in theory. I have a couple of concerns.</div><div><ol class="MailOutline"><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><li>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.</li><li>We would need to document our index somewhere similar to <a href="http://nodejs.org/api/documentation.html#documentation_stability_index">http://nodejs.org/api/documentation.html#documentation_stability_index</a></li></ol><div><br></div><blockquote type="cite"><br>-- <br>qmx<br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote></div><br></body></html>