Hi Justin, We have yet to come up with our first Apache release. We're having issues wrapping our heads around how to come up with our LICENSE file given the number of dependencies we have on the Javascript side. Since we package the JS bundle along with our Python application, it seems like we'll have to come up with either a programmatic way to extract the LICENSE info, or ship the application without the JS deps, and provide instruction has to how to fetch and build the package deps, which isn't very convenient. We also have some minor deps on GPL lib, one of which we need to get clarity as to how to to handle them. It's related to the "chardet" sub dependency of the Pypi requests library.
Clearly we need to come up with a plan for our first Apache release. I'll bring this up at the next committer meeting (this upcoming Friday) Max On Fri, Aug 31, 2018 at 3:56 PM Justin Mclean <[email protected]> wrote: > Hi, > > I was taking at look at incubating projects and noticed that you you don't > seem to be following the required release process. I don't see for instance > any VOTE threads [3] or checking of the release by the Incubator PMC [4] > and it looks like you are publishing releases elsewhere [4][1] and there > are no releases in the release ares. [5][6] > > I'm not familiar with your project so hopefully I'm mistaken (and > apologies in advance if I am), but I think it would be good if you could > address this in your podling report which is due shortly. > > Thanks, > Justin > > 1.https://github.com/apache/incubator-superset/releases > 3. http://www.apache.org/legal/release-policy.html#release-approval > 4.http://www.apache.org/legal/release-policy.html#publication > 5.http://www.apache.org/legal/release-policy.html#release-distribution > 6.https://dist.apache.org/repos/dist/release/incubator/superset >
