Well, we could use JIRA as you suggested, but for starters, a list of issues in a separate email thread might be more efficient. I've lost track of what the issues are since some, like the npm distro is no longer an issue (I think).
-Alex From: "omup...@gmail.com<mailto:omup...@gmail.com>" <omup...@gmail.com<mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala <bigosma...@gmail.com<mailto:bigosma...@gmail.com>> Date: Thursday, September 15, 2016 at 6:47 PM To: Alex Harui <aha...@adobe.com<mailto:aha...@adobe.com>> Cc: "dev@flex.apache.org<mailto:dev@flex.apache.org>" <dev@flex.apache.org<mailto:dev@flex.apache.org>> Subject: Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released On Thu, Sep 15, 2016 at 6:21 PM, Alex Harui <aha...@adobe.com<mailto:aha...@adobe.com>> wrote: Some issues are more controversial than others. The controversial ones should be decided before committing changes. Fair enough. But that said, I do see Justin's point that he does not want to make the changes if there is a threat of a veto. How can we separate out things so that the easy to fix ones don't end up clubbed together with controversial ones? In other words, how can we make it easier for Justin to go ahead and JFDI? Thanks, Om Sent from my LG G3, an AT&T 4G LTE smartphone ------ Original message------ From: OmPrakash Muppirala Date: Thu, Sep 15, 2016 5:41 PM To: dev@flex.apache.org<mailto:dev@flex.apache.org>; Subject:Re: [DRAFT] Apache FlexJS 0.7.0 and Apache Flex FalconJX 0.7.0 Released On Thu, Sep 15, 2016 at 4:42 PM, Justin Mclean <jus...@classsoftware.com<mailto:jus...@classsoftware.com>> wrote: > Hi, > > > Justin, any reason you did not fix the issues yourself? Were you > expecting > > someone else to fix them? > > If I had changed LICENSE/NOTICE without discussion it’s probable that my > changes would be vetoed. > I doubt that would happen. Maybe you should try fixing them and see what happens? ;-) Thanks, Om > > > Also, why were no JIRA tickets filed? > > For these exact issue no a sI had expected it to be resolved before the RC > was made. I usually raise them after the release so it's not forgotten > about before the next one - for instance [1] > I think you should create tickets for each licensing issue you bring up. a) It would be easier for anyone else (ex. Legal folks) to come take a look and quickly give an opinion and b) We have a record that we did actually discuss this issue and made an effort to resolve the issue. Thanks, Om > > Thanks, > Justin > > 1. https://issues.apache.org/jira/browse/FLEX-35058
