ktmud edited a comment on issue #12631: URL: https://github.com/apache/superset/issues/12631#issuecomment-768138854
@junlincc Agree with most of what you said and totally understand the desire of having a stable product and making decisions based on more user feedbacks. However, this design does block some new users from adding a second metric, at least initially, as evidenced by our user feedback. I'd consider anything that already has a negatively user feedback (even just one) to be relatively high priority... We don't have to agree with every user feedback, but we should at least consider if there are better solutions to their problems. If yes, then why not go ahead with it? If someone comes up with a better solution later, we can always iterate. I guess what I didn't fully get is why can't we put this into the "OK to implement, but no need to prioritize" bucket, rather than "hold until further design review which nobody know when will happen" bucket, when there is already enough consensus? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
