Yeah, sorry Mike. I wasn't sure of the protocol here. I'll keep that in mind from the next time.
On Tue, Aug 11, 2015 at 3:18 AM, Michael McCandless <[email protected]> wrote: > On Mon, Aug 10, 2015 at 5:30 PM, Chris Hostetter > <[email protected]> wrote: >> >> : I'm confused: this issue isn't a blocker? Why are we holding up a >> : release for non-blocker issues? >> >> If i understand correctly, SOLR-7838 is (part of) a "feature" and by >> definition not a blocker -- but after being committed Shalin noticed that >> the "syntax" of the user facing API introduced in that feature is >> problematic and the folks involved wnat to try and fix it before release >> because otherwise it becomes a back compat nightmare.... >> >> https://issues.apache.org/jira/browse/SOLR-7838?focusedCommentId=14680361&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14680361 >> >> ...not sure if marking this "feature" as a "blocker" at that point would >> have really been a good process to follow? >> >> (perhaps a new "Blocker: Bug" should have been created? "Need to fix >> permissions API syntax before 5.3 release otherwise it's a backcompat >> nightmare" ?) > > OK thanks for the summary Hoss, I didn't read the comments on the > issue to see the backstory. > > I do think the right thing to do in this case is to reopen the issue, > mark it blocker at that point, and in the comment explain why a new > feature became a release blocker ... either that or a new issue ... > > And thank you Shalin for reviewing a new feature before it's released :) > > Mike McCandless > > http://blog.mikemccandless.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Regards, Shalin Shekhar Mangar. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
