Nicolas: Your earlier comment on metrics that make a feature more palatable is very good.
Can you take a look at and see if there is more information you want to gather ? https://issues.apache.org/jira/browse/HBASE-4120?focusedCommentId=13143315&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13143315 Stack: Once a feature goes to production at company X, they would dedicate personnel on maintaining the feature. Cheers On Wed, Nov 2, 2011 at 8:17 PM, Stack <st...@duboce.net> wrote: > On Wed, Nov 2, 2011 at 5:12 PM, Nicolas Spiegelberg <nspiegelb...@fb.com> > wrote: > > I agree with Todd's sentiments on unnecessarily coupling feature priority > > with the availability of a patch. There's patches that we've developed > > internally, then threw away because we couldn't tie it to a production > use > > case or thought a better design might be necessary. There's also patches > > that we've had simmering out for a couple weeks so we could think about > it > > and cross-talk. Every new feature adds to the complexity of an > > already-complex system. We should make sure the feature has demand. > > > > Another factor that I think we should consider when taking on big > features, and I've heard a version of this from you Nicolas, is > whether the feature contributor will be around post commit to fix bugs > that pop up post-commit. > > St.Ack >
