Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
HI, > I replaced the babytux image by one I got here > https://pixabay.com/vectors/toddlers-babies-children-303904/, now how do I > expose the license for the image? Assuming the license is compatible you would add the text of the license (or if it is long a pointer to a file containing the text) in the LICENSE file. I think the license is this? [1] While “free" it does contain some restrictions beyond what the ALv2 allows. It’s not listed as a category A or B license [2] so IMO it would be best to ask legal discuss to see if it’s OK to use it. It might be easer to find another image under a compatible license e.g public domain / CC0 [4] or CC BY-SA 4.0 [3]. Thanks, Justin 1. https://pixabay.com/service/license/ 2. https://apache.org/legal/resolved.html 3, https://apache.org/legal/resolved.html#cc-sa 4. https://apache.org/legal/resolved.html#handling-public-domain-licensed-works - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
I replaced the babytux image by one I got here https://pixabay.com/vectors/toddlers-babies-children-303904/, now how do I expose the license for the image? Max On Fri, May 17, 2019 at 4:36 PM Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > Making progress here > https://github.com/apache/incubator-superset/pull/7539 > > Many of the issues have been addressed in `master` but can't easily be > cherry-picked into 0.32, so I'm thinking about skipping to 0.33 instead > that has been cut 1 month ago. So the next attempt will be `0.33.0rc1` > > Max > > On Tue, Apr 30, 2019 at 5:34 PM Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > >> FYI I'm working integrating the feedback and working towards the next RC. >> >> I started working on build instructions and things were getting quite >> complex while building from source, and adding steps like the os-level >> deps, creating the `.po` files, building the JS, and these instructions >> tend to not be perfectly reproducible across environments, so I decided to >> write a Dockerfile that builds from source instead of docs or a bash >> script. Eventually that can evolve to run assertions on the build (running >> tests, checking keys, ...) in a reproducible fashion. The built package can >> be extracted from the docker image, or the Dockerfile can be used as a >> reference if someone needed to make an equivalent bash script. >> >> Similarly, I'm thinking about using a Dockerfile for the process of >> packaging the source release, since the process forces a "git clean" that >> can be harmful to existing environments. >> >> Max >> >> On Sat, Apr 27, 2019 at 1:40 AM wrote: >> >>> Hi, >>> >>> > - they are not? I dont follow? How would you suggest making them >>> binary then? >>> >>> Ask on legal discuss, I don’t think they will be allowed in a source >>> release, but it may be possible given maps are not likely to change much. >>> Worse case you may have to find some maps under a different license or ask >>> for them to be relicensed under a more friendly license. >>> >>> > On the other hand the initial picture you painted seemed quite grim >>> but these issues can be overcome relatively easy. >>> >>> All of the issues are easy to fix one way or another, this stuff is hard >>> to get right first time around, but gets easier. >>> >>> Thanks, >>> Justin >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>>
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Making progress here https://github.com/apache/incubator-superset/pull/7539 Many of the issues have been addressed in `master` but can't easily be cherry-picked into 0.32, so I'm thinking about skipping to 0.33 instead that has been cut 1 month ago. So the next attempt will be `0.33.0rc1` Max On Tue, Apr 30, 2019 at 5:34 PM Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > FYI I'm working integrating the feedback and working towards the next RC. > > I started working on build instructions and things were getting quite > complex while building from source, and adding steps like the os-level > deps, creating the `.po` files, building the JS, and these instructions > tend to not be perfectly reproducible across environments, so I decided to > write a Dockerfile that builds from source instead of docs or a bash > script. Eventually that can evolve to run assertions on the build (running > tests, checking keys, ...) in a reproducible fashion. The built package can > be extracted from the docker image, or the Dockerfile can be used as a > reference if someone needed to make an equivalent bash script. > > Similarly, I'm thinking about using a Dockerfile for the process of > packaging the source release, since the process forces a "git clean" that > can be harmful to existing environments. > > Max > > On Sat, Apr 27, 2019 at 1:40 AM wrote: > >> Hi, >> >> > - they are not? I dont follow? How would you suggest making them binary >> then? >> >> Ask on legal discuss, I don’t think they will be allowed in a source >> release, but it may be possible given maps are not likely to change much. >> Worse case you may have to find some maps under a different license or ask >> for them to be relicensed under a more friendly license. >> >> > On the other hand the initial picture you painted seemed quite grim but >> these issues can be overcome relatively easy. >> >> All of the issues are easy to fix one way or another, this stuff is hard >> to get right first time around, but gets easier. >> >> Thanks, >> Justin >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
FYI I'm working integrating the feedback and working towards the next RC. I started working on build instructions and things were getting quite complex while building from source, and adding steps like the os-level deps, creating the `.po` files, building the JS, and these instructions tend to not be perfectly reproducible across environments, so I decided to write a Dockerfile that builds from source instead of docs or a bash script. Eventually that can evolve to run assertions on the build (running tests, checking keys, ...) in a reproducible fashion. The built package can be extracted from the docker image, or the Dockerfile can be used as a reference if someone needed to make an equivalent bash script. Similarly, I'm thinking about using a Dockerfile for the process of packaging the source release, since the process forces a "git clean" that can be harmful to existing environments. Max On Sat, Apr 27, 2019 at 1:40 AM wrote: > Hi, > > > - they are not? I dont follow? How would you suggest making them binary > then? > > Ask on legal discuss, I don’t think they will be allowed in a source > release, but it may be possible given maps are not likely to change much. > Worse case you may have to find some maps under a different license or ask > for them to be relicensed under a more friendly license. > > > On the other hand the initial picture you painted seemed quite grim but > these issues can be overcome relatively easy. > > All of the issues are easy to fix one way or another, this stuff is hard > to get right first time around, but gets easier. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, > - they are not? I dont follow? How would you suggest making them binary then? Ask on legal discuss, I don’t think they will be allowed in a source release, but it may be possible given maps are not likely to change much. Worse case you may have to find some maps under a different license or ask for them to be relicensed under a more friendly license. > On the other hand the initial picture you painted seemed quite grim but these > issues can be overcome relatively easy. All of the issues are easy to fix one way or another, this stuff is hard to get right first time around, but gets easier. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, - okay :-) I'm a bit confused here but fine - they are not? I dont follow? How would you suggest making them binary then? And yes I agree there are more pressing issues. The roboto fonts are in fact ALv2 (https://github.com/apache/fineract-site/tree/master/font/roboto ), the glyphs fonts are the more serious ones and the incubator name. On the other hand the initial picture you painted seemed quite grim but these issues can be overcome relatively easy. Cheers Bolke Sent from my iPhone > On 27 Apr 2019, at 09:45, jus...@classsoftware.com wrote: > > Hi, > >> Can I assume that we are doing the right thing now for the CC-BY 4.0 in >> NOTICE and LICENSE. > > You're not :-) but it not a major issue as as I said, it doesn’t need to be > fixed in this release. If files were modified then you might need to list > those changes in NOTICE but then AFAIK it’s not going to be ALv2 compatible. > >> On the GeoJSON, these are actually compiled from the shape files that Diva >> GIS makes available. So while they are human readable, I would consider >> these ‘binary’? > > Well they not are they and that's the issue. I suggest you ask on legal > discuss about this on what to do and move forward. But there are more serious > issues e.g. incubating missing from name and the font licensing issue that I > think also need to be considered. > > Thanks, > Justin
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, > Can I assume that we are doing the right thing now for the CC-BY 4.0 in > NOTICE and LICENSE. You're not :-) but it not a major issue as as I said, it doesn’t need to be fixed in this release. If files were modified then you might need to list those changes in NOTICE but then AFAIK it’s not going to be ALv2 compatible. > On the GeoJSON, these are actually compiled from the shape files that Diva > GIS makes available. So while they are human readable, I would consider these > ‘binary’? Well they not are they and that's the issue. I suggest you ask on legal discuss about this on what to do and move forward. But there are more serious issues e.g. incubating missing from name and the font licensing issue that I think also need to be considered. Thanks, Justin
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi Justin, Can I assume that we are doing the right thing now for the CC-BY 4.0 in NOTICE and LICENSE. The license does ask for “something beyond” and referring to it in NOTICE seems to me a “reasonable manner”. On the GeoJSON, these are actually compiled from the shape files that Diva GIS makes available. So while they are human readable, I would consider these ‘binary’? Cheers Bolke On 27 April 2019 at 01:56:57, Justin Mclean (jus...@classsoftware.com) wrote: Hi, > "Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.” License stuff goes in LICENSE. If the license ask for anything beyond that and it not covered by license then they go in NOTICE. [1] Other other things that go in NOTICE are relocated copyrights and content from other NOTICE files. > Do you consider the GeoJSON not to be binary? (In ./countries) Yes for instance take a look at these files [2] and you see they are in plain text son format and are not binary. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#mod-notice 2. apache-superset-0.32.0rc2/superset/assets/src/visualizations/CountryMap/countries/*.geojson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, > "Attribution — You must give appropriate credit, provide a link to the > license, and indicate if changes were made. You may do so in any reasonable > manner, but not in any way that suggests the licensor endorses you or your > use.” License stuff goes in LICENSE. If the license ask for anything beyond that and it not covered by license then they go in NOTICE. [1] Other other things that go in NOTICE are relocated copyrights and content from other NOTICE files. > Do you consider the GeoJSON not to be binary? (In ./countries) Yes for instance take a look at these files [2] and you see they are in plain text son format and are not binary. Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#mod-notice 2. apache-superset-0.32.0rc2/superset/assets/src/visualizations/CountryMap/countries/*.geojson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi - From time to time podlings do not put incubating or incubator in the name. The clutch analysis does catch this in the daily scan of the release distribution areas. On https://incubator.apache.org/clutch/ look down towards the bottom for “Other Issues”. On a podling clutch analysis page these show as: https://incubator.apache.org/clutch/toree.html#errata Regards, Dave > On Apr 25, 2019, at 7:39 PM, Justin Mclean wrote: > > - incubating is missing from name - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi Justin The CC-BY 4.0 is included in both NOTICE and LICENSE due to " Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use." Is that is misinterpretation then? Do you consider the GeoJSON not to be binary? (In ./countries) Cheers Bolke Sent from my iPhone > On 26 Apr 2019, at 16:05, Justin Mclean wrote: > > Hi, > >> The GIS data is under CC BY 4.0 see here: >> >> Hence the reference to this license. > > Which should be in LICENSE not NOTICE but not a major issue. > >> According to https://apache.org/legal/resolved.html it is fine to include >> this in binary form (whether it can be as part of a source release I leave >> that up to you, it’s a bit of a grey area to me in this case). > > Which is fine, except it’s not in binary form in the source release. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, > The GIS data is under CC BY 4.0 see here: > > Hence the reference to this license. Which should be in LICENSE not NOTICE but not a major issue. > According to https://apache.org/legal/resolved.html it is fine to include > this in binary form (whether it can be as part of a source release I leave > that up to you, it’s a bit of a grey area to me in this case). Which is fine, except it’s not in binary form in the source release. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Also on [5] and [6] the license location is here https://github.com/syntagmatic/parallel-coordinates which includes divgrid.js in examples/lib as part of the package and from the same author. Cheers Bolke Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 15:14 heeft Bolke de Bruin het > volgende geschreven: > > Additionally > > [3] Is CC-BY 4.0 as mentioned > [4] is in licenses/ and states the correct license. > [5] [6] ([6] is equal to [9]) are from the same author and the correct > license (BSD-3) is included in licenses/ (see also: > http://bl.ocks.org/syntagmatic/3150059 - scroll down please). > > All above licenses are mentioned in LICENSE.txt > > Other items I leave up to the release manager to answer. > > Bolke. > > Verstuurd vanaf mijn iPad > >> Op 26 apr. 2019 om 10:03 heeft Bolke de Bruin het >> volgende geschreven: >> >> Hi Justin, >> >> The GIS data is under CC BY 4.0 see here: >> >> https://journals.plos.org/plosone/article/file?type=supplementary=info:doi/10.1371/journal.pone.0151586.s002 >> >> Hence the reference to this license. According to >> https://apache.org/legal/resolved.html it is fine to include this in binary >> form (whether it can be as part of a source release I leave that up to you, >> it’s a bit of a grey area to me in this case). >> >> Cheers >> Bolke >> >> >> Verstuurd vanaf mijn iPad >> >>> Op 26 apr. 2019 om 06:20 heeft Sheng Wu het >>> volgende geschreven: >>> >>> Hi Justin >>> >>> I mean these two are very important and should be fixed. Sorry for not >>> clear enough. >>> >>> Sheng Wu 吴晟 >>> >>> Apache SkyWalking, ShardingSphere, Zipkin >>> Twitter, wusheng1108 >>> >>> >>> Justin Mclean 于2019年4月26日周五 下午12:16写道： >>> Hi, It a little unclear to me if your are commenting on the release check list or the Superset release here. > 1. Missing licensing information Well IMO it depends on the serenity IMO missing one or two MIT or BSD licenses in a podling release is generally a fix next release type of issue as they are permissive licenses and often the license is included (as a header) just not clearly indicated that’s it’s included, so it’s more an ASF policy issue than an actual licensing issue. > 2. Source release may contained compiled code I’m still not sure it can. In the past I’ve alway voted -1 on this issue, but it's recently been suggested, that we go easier on podlings releases particularly their first one. It is still however unknown if the board (who are responsible for release policy) or infra (who are responsible for distribution policy) would actually allow this. So far that exact situation has not come and I not been able to get a clear answer from others on this. The incubator (and its PMC) don’t set those policies. [1][2] Thanks, Justin 1. http://www.apache.org/legal/release-policy.html 2. https://www.apache.org/dev/release-distribution - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Additionally [3] Is CC-BY 4.0 as mentioned [4] is in licenses/ and states the correct license. [5] [6] ([6] is equal to [9]) are from the same author and the correct license (BSD-3) is included in licenses/ (see also: http://bl.ocks.org/syntagmatic/3150059 - scroll down please). All above licenses are mentioned in LICENSE.txt Other items I leave up to the release manager to answer. Bolke. Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 10:03 heeft Bolke de Bruin het > volgende geschreven: > > Hi Justin, > > The GIS data is under CC BY 4.0 see here: > > https://journals.plos.org/plosone/article/file?type=supplementary=info:doi/10.1371/journal.pone.0151586.s002 > > Hence the reference to this license. According to > https://apache.org/legal/resolved.html it is fine to include this in binary > form (whether it can be as part of a source release I leave that up to you, > it’s a bit of a grey area to me in this case). > > Cheers > Bolke > > > Verstuurd vanaf mijn iPad > >> Op 26 apr. 2019 om 06:20 heeft Sheng Wu het >> volgende geschreven: >> >> Hi Justin >> >> I mean these two are very important and should be fixed. Sorry for not >> clear enough. >> >> Sheng Wu 吴晟 >> >> Apache SkyWalking, ShardingSphere, Zipkin >> Twitter, wusheng1108 >> >> >> Justin Mclean 于2019年4月26日周五 下午12:16写道： >> >>> Hi, >>> >>> It a little unclear to me if your are commenting on the release check list >>> or the Superset release here. >>> 1. Missing licensing information >>> >>> Well IMO it depends on the serenity IMO missing one or two MIT or BSD >>> licenses in a podling release is generally a fix next release type of issue >>> as they are permissive licenses and often the license is included (as a >>> header) just not clearly indicated that’s it’s included, so it’s more an >>> ASF policy issue than an actual licensing issue. >>> 2. Source release may contained compiled code >>> >>> I’m still not sure it can. In the past I’ve alway voted -1 on this issue, >>> but it's recently been suggested, that we go easier on podlings releases >>> particularly their first one. It is still however unknown if the board (who >>> are responsible for release policy) or infra (who are responsible for >>> distribution policy) would actually allow this. So far that exact situation >>> has not come and I not been able to get a clear answer from others on this. >>> The incubator (and its PMC) don’t set those policies. [1][2] >>> >>> Thanks, >>> Justin >>> >>> 1. http://www.apache.org/legal/release-policy.html >>> 2. https://www.apache.org/dev/release-distribution >>> >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>>
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi Justin, The GIS data is under CC BY 4.0 see here: https://journals.plos.org/plosone/article/file?type=supplementary=info:doi/10.1371/journal.pone.0151586.s002 Hence the reference to this license. According to https://apache.org/legal/resolved.html it is fine to include this in binary form (whether it can be as part of a source release I leave that up to you, it’s a bit of a grey area to me in this case). Cheers Bolke Verstuurd vanaf mijn iPad > Op 26 apr. 2019 om 06:20 heeft Sheng Wu het > volgende geschreven: > > Hi Justin > > I mean these two are very important and should be fixed. Sorry for not > clear enough. > > Sheng Wu 吴晟 > > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > > > Justin Mclean 于2019年4月26日周五 下午12:16写道： > >> Hi, >> >> It a little unclear to me if your are commenting on the release check list >> or the Superset release here. >> >>> 1. Missing licensing information >> >> Well IMO it depends on the serenity IMO missing one or two MIT or BSD >> licenses in a podling release is generally a fix next release type of issue >> as they are permissive licenses and often the license is included (as a >> header) just not clearly indicated that’s it’s included, so it’s more an >> ASF policy issue than an actual licensing issue. >> >>> 2. Source release may contained compiled code >> >> I’m still not sure it can. In the past I’ve alway voted -1 on this issue, >> but it's recently been suggested, that we go easier on podlings releases >> particularly their first one. It is still however unknown if the board (who >> are responsible for release policy) or infra (who are responsible for >> distribution policy) would actually allow this. So far that exact situation >> has not come and I not been able to get a clear answer from others on this. >> The incubator (and its PMC) don’t set those policies. [1][2] >> >> Thanks, >> Justin >> >> 1. http://www.apache.org/legal/release-policy.html >> 2. https://www.apache.org/dev/release-distribution >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi Justin I mean these two are very important and should be fixed. Sorry for not clear enough. Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Justin Mclean 于2019年4月26日周五 下午12:16写道： > Hi, > > It a little unclear to me if your are commenting on the release check list > or the Superset release here. > > > 1. Missing licensing information > > Well IMO it depends on the serenity IMO missing one or two MIT or BSD > licenses in a podling release is generally a fix next release type of issue > as they are permissive licenses and often the license is included (as a > header) just not clearly indicated that’s it’s included, so it’s more an > ASF policy issue than an actual licensing issue. > > > 2. Source release may contained compiled code > > I’m still not sure it can. In the past I’ve alway voted -1 on this issue, > but it's recently been suggested, that we go easier on podlings releases > particularly their first one. It is still however unknown if the board (who > are responsible for release policy) or infra (who are responsible for > distribution policy) would actually allow this. So far that exact situation > has not come and I not been able to get a clear answer from others on this. > The incubator (and its PMC) don’t set those policies. [1][2] > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html > 2. https://www.apache.org/dev/release-distribution > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, It a little unclear to me if your are commenting on the release check list or the Superset release here. > 1. Missing licensing information Well IMO it depends on the serenity IMO missing one or two MIT or BSD licenses in a podling release is generally a fix next release type of issue as they are permissive licenses and often the license is included (as a header) just not clearly indicated that’s it’s included, so it’s more an ASF policy issue than an actual licensing issue. > 2. Source release may contained compiled code I’m still not sure it can. In the past I’ve alway voted -1 on this issue, but it's recently been suggested, that we go easier on podlings releases particularly their first one. It is still however unknown if the board (who are responsible for release policy) or infra (who are responsible for distribution policy) would actually allow this. So far that exact situation has not come and I not been able to get a clear answer from others on this. The incubator (and its PMC) don’t set those policies. [1][2] Thanks, Justin 1. http://www.apache.org/legal/release-policy.html 2. https://www.apache.org/dev/release-distribution - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi In Justin's checked list, you hope the community to confirm at least for this first release. 1. Missing licensing information 2. Source release may contained compiled code And add `incubating` in the name. Please make sure doesn't include the license against Apache 2.0, Sheng Wu 吴晟 Apache SkyWalking, ShardingSphere, Zipkin Twitter, wusheng1108 Justin Mclean 于2019年4月26日周五 上午10:49写道： > Hi, > > Normally I would be -1 binding as there’s a number of issues here, however > the most serious one for a first release is that you are missing incubating > from the artefact name. The artefacts can be renamed without changing the > hash or anything else, if you rename I’ll change my vote to +1. Other IPMC > members may think the issue are more serious and may also vote -1. You may > need to check with legal if it OK to distribute this release given the font > licensing issue. > > The PPMC could also decide to not release this and cancel the vote because > of the issues below and instead fix them and make another RC to vote on. > > Using a checklist like this [2] when voting on releases might help, you > can also ask the IPMC to take a look at a release before putting it up for > vote here.That’s probably a good thing to do for a first release. > > I checked: > - incubating is missing from name > - signatures and hashes good > - DISCLAIMER exists > - LICENSE is missing a few licenses (see below) > - NOTICE should not include LICENSE information e.g The line about CC 4.0. > This may need to be removed. Also this content may be Category X and this > can’t included in a source release. [11] > - Some 3rd party code have headers with "[LICENSE TBD]” [4][5][6][7][9] > which seems odd > - The ASF headers on a number of files are not correct e.g the file [13] > and other under that directory (search for COPYRIGHT 2016 and and COPYRIGHT > 2017 and COPYRIGHT 2018) Or are these files not actually licensed to the > ASF? > - Source release may contained compiled code e.g [20] my understanding is > that a .mo file is compiled from the .po file. I not sure if it could be > classified as code however, but even if that is so it may be best to remove > them from the source release. > > There is a few bits of missing licensing information: > - How is the map date here licensed? [3] Is it from > http://www.diva-gis.org/Data? I can see there is a credit in the code > that has a link to https://bl.ocks.org/john-guerra. How is that code > licensed? > - This file [7] is missing from LICENSE I assume it’s public domain? [8] > - This file [9] is licensed how? It seems to come from here [10] which > says to contact the author for a license. > - How is this image [14] licensed? (One reference I found said it could > only be used for personal use [21]) > - LICENSE is missing license information for these fonts > [15][16][17][18][19] The license for Glyphicons Halflings is complex and in > this context (outside of bootstrap) a commercial license may be needed [22] > and so it can’t be included. > > Some other improvements that could be made: > - The LICENSE fieldworker is a little odd with headings like BSD 2-Clause > licenses with noting under them, people (or tools) may incorrectly assume > that it does contain BSD 2-Clause licensed code. > - Make vote link link in future emails to lists.apache,org > - Sign release with an apache.org email address > - This [12] has copyright 2018 when it shovel be 2019 > > Thanks, > Justin > > 1. https://incubator.apache.org/policy/incubation.html#releases > 2. > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > 3. > apache-superset-0.32.0rc2/superset/assets/src/visualizations/CountryMap/* > 4. > apache-superset-0.32.0rc2/superset/assets/vendor/cal-heatmap/cal-heatmap.js > / .css > 5 > apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/d3.parcoords.js > / .css > 6. > apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js > 7 apache-superset-0.32.0rc2/superset/assets/vendor/pygments.css > 8. https://github.com/richleland/pygments-css/blob/master/UNLICENSE.txt > 9. > ./apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js > 10. http://bl.ocks.org/syntagmatic/3687826 > 11. http://www.tavfrna.incubator.apache.org/legal/resolved.html#cc-sa > 12. ./apache-superset-0.32.0rc2/docs/conf.py > 13. ./apache-superset-0.32.0rc2/superset/translations/messages.pot > 14. ./apache-superset-0.32.0rc2/superset/assets/images/babytux.jpg > 15. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/Roboto-Regular.woff > 16. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/Roboto-Regular.woff2 > 17. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.ttf > 18. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff > 19. > apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff2 > 20 >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Hi, Normally I would be -1 binding as there’s a number of issues here, however the most serious one for a first release is that you are missing incubating from the artefact name. The artefacts can be renamed without changing the hash or anything else, if you rename I’ll change my vote to +1. Other IPMC members may think the issue are more serious and may also vote -1. You may need to check with legal if it OK to distribute this release given the font licensing issue. The PPMC could also decide to not release this and cancel the vote because of the issues below and instead fix them and make another RC to vote on. Using a checklist like this [2] when voting on releases might help, you can also ask the IPMC to take a look at a release before putting it up for vote here.That’s probably a good thing to do for a first release. I checked: - incubating is missing from name - signatures and hashes good - DISCLAIMER exists - LICENSE is missing a few licenses (see below) - NOTICE should not include LICENSE information e.g The line about CC 4.0. This may need to be removed. Also this content may be Category X and this can’t included in a source release. [11] - Some 3rd party code have headers with "[LICENSE TBD]” [4][5][6][7][9] which seems odd - The ASF headers on a number of files are not correct e.g the file [13] and other under that directory (search for COPYRIGHT 2016 and and COPYRIGHT 2017 and COPYRIGHT 2018) Or are these files not actually licensed to the ASF? - Source release may contained compiled code e.g [20] my understanding is that a .mo file is compiled from the .po file. I not sure if it could be classified as code however, but even if that is so it may be best to remove them from the source release. There is a few bits of missing licensing information: - How is the map date here licensed? [3] Is it from http://www.diva-gis.org/Data? I can see there is a credit in the code that has a link to https://bl.ocks.org/john-guerra. How is that code licensed? - This file [7] is missing from LICENSE I assume it’s public domain? [8] - This file [9] is licensed how? It seems to come from here [10] which says to contact the author for a license. - How is this image [14] licensed? (One reference I found said it could only be used for personal use [21]) - LICENSE is missing license information for these fonts [15][16][17][18][19] The license for Glyphicons Halflings is complex and in this context (outside of bootstrap) a commercial license may be needed [22] and so it can’t be included. Some other improvements that could be made: - The LICENSE fieldworker is a little odd with headings like BSD 2-Clause licenses with noting under them, people (or tools) may incorrectly assume that it does contain BSD 2-Clause licensed code. - Make vote link link in future emails to lists.apache,org - Sign release with an apache.org email address - This [12] has copyright 2018 when it shovel be 2019 Thanks, Justin 1. https://incubator.apache.org/policy/incubation.html#releases 2. https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist 3. apache-superset-0.32.0rc2/superset/assets/src/visualizations/CountryMap/* 4. apache-superset-0.32.0rc2/superset/assets/vendor/cal-heatmap/cal-heatmap.js / .css 5 apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/d3.parcoords.js / .css 6. apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js 7 apache-superset-0.32.0rc2/superset/assets/vendor/pygments.css 8. https://github.com/richleland/pygments-css/blob/master/UNLICENSE.txt 9. ./apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js 10. http://bl.ocks.org/syntagmatic/3687826 11. http://www.tavfrna.incubator.apache.org/legal/resolved.html#cc-sa 12. ./apache-superset-0.32.0rc2/docs/conf.py 13. ./apache-superset-0.32.0rc2/superset/translations/messages.pot 14. ./apache-superset-0.32.0rc2/superset/assets/images/babytux.jpg 15. apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/Roboto-Regular.woff 16. apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/Roboto-Regular.woff2 17. apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.ttf 18. apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff 19. apache-superset-0.32.0rc2/superset/assets/stylesheets/fonts/glyphicons-halflings-regular.woff2 20 apache-superset-0.32.0rc2/superset/translations/de/LC_MESSAGES/messages.mo 21. https://www.pngfly.com/png-79pbyi/ 22. https://www.glyphicons.com/license/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
+1 (binding) * Checked DISCLAIMER/ LICENSE/ NOTICE, * Checked headers * Verified sig (Only Max's key is in there, we should probably have others roll a release too in the future) * Spotchecked licenses * Verified md512 hash. -Jakob On Wed, Apr 24, 2019 at 4:14 PM Alan Gates wrote: > > Forwarding my +1 from the dev list. Checked the NOTICE, LICENSE, and > DISCLAIMER files. Did a quick check that everything had appropriate Apache > License headers, and I didn't find any binaries in the RC. > > Alan. > > On Wed, Apr 24, 2019 at 1:37 PM Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > > > Dear all, > > > > The source release 0.32.0 RC2 for Apache Superset is baked and available > > at: > > https://dist.apache.org/repos/dist/dev/incubator/superset/, public > > keys are available > > at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS > > > > This is the second ASF release candidate of Superset (!)* We're still > > ironing out our release process, so please bear with us and help if you > > can* > > . > > > > Here's link to original successful VOTE thread on dev@: > > > > http://mail-archives.apache.org/mod_mbox/superset-dev/201904.mbox/%3ccah7q75ip1lzq61+6yvfoqvb2nser8vhsa5rca87uzrrbpj9...@mail.gmail.com%3E > > > > As I went along, I documented the process in RELEASING.md in the repo, > > latest edits here https://github.com/apache/incubator-superset/pull/7329 > > > > For context (and similarly to 0.31) the `0.32` release branch was cut at > > SHA 1fece0d2f, that was merged on master on Jan 22nd. From that common > > ancestor, the following list of commit was added as cherry-picks. The SHAs > > in the list bellow reference the cherries on the release branch, PR number > > are available to get more details. > > > > New commits since 0.32.0rc1 *in bold:* > > > > *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2* > > *3e6f6848 Add disclaimer and remove counter (#6738)* > > c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1 > > b89cdbdc RELEASING.md from master > > 0e23f2e6 Add sign.sh > > 21804346 [load_examples] download data at runtime (#7314) > > b32d5900 Remove LICENSE entry around dataset (#7318) > > b3aa5633 (release--0.31) 0.31rc23 > > 24a595f4 bugfix: improve 'Time Table' (#6959) > > c70abbed 0.31rc22 > > dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244) > > 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198) > > (#7242) > > a9d54894 0.31.0rc21 > > b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message modal > > (#7179) > > 2da9613f Update __init__.py (#7166) > > 538da2e3 0.31.0.rc20 > > 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145) > > 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144) > > daf2b8e5 Bump python lib croniter to an existing version (#7132) > > eb4c1355 Use metric name instead of metric in filter box (#7106) > > 2ff721ae handle null column_name in sqla and druid models > > e83a07d3 [forms] Fix handling of NULLs > > 76d26f37 0.31.0.rc19 > > fe78b4ec Fix filter_box migration PR #6523 (#7066) > > c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined query > > (#7029) > > b64a452a [sql lab] improve table name detection in free form SQL (#6793) > > 2357c4aa Adding custom control overrides (#6956) > > 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963) > > 5d8dd142 [csv-upload] Fixing message encoding (#6971) > > f454dedd [main] Disable resetting main DB attributes (#6845) > > e967b268 [sqla] Fixing order-by for non-inner-joins (#6862) > > a5d9a4e0 Adding template_params to datasource editor for sqla tables > > (#6869) > > 6b895413 [datasource] Ensuring consistent behavior of datasource > > editing/saving. (#7037) > > 8ef2789f Adding warning message for sqllab save query (#7028) > > 0ebdb564 fix inaccurate data calculation with adata rolling and > > contribution (#7035) > > b3af6a26 [fix] explore chart from dashboard missed slice title (#7046) > > c54b067c [db-engine-spec] Aligning Hive/Presto partition logic (#7007) > > bd65942e Changing time table viz to pass formatTime a date (#7020) > > 50accda9 [fix] Cursor jumping when editing chart and dashboard titles > > (#7038) > > 5ace5769 0.31.0rc17 > > 927a5846 [WIP] fix user specified JSON metadata not updating dashboard on > > refresh (#7027) > > fafb824d 0.31.0rc16 > > 7b72985e [fix] /superset/slice/id url is too long (#6989) > > b497d9e7 fix dashboard links in welcome page (#6756) > > c42afa11 0.31.0rc15 > > 35c55278 Enhancement of query context and object. (#6962) > > 1c41020c Split tags migration (#7002) > > ec7a0b22 0.31.0rc14 > > 4655cb4c Remove Cypress from package.json (#6912) > > fb8e3208 0.31.0rc13 > > b4cbe13d VIZ-190 fix (#6958) > > 5b7b22fd 0.31.0rc12 > > 51804229 Fix deck.gl form data (#6953) > > 9939a52d 0.31.0rc11 > > c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix > > rendering regression from the introduction of bignumber (#6937) > > 9940d30a 0.31.0rc10 > >
Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Forwarding my +1 from the dev list. Checked the NOTICE, LICENSE, and DISCLAIMER files. Did a quick check that everything had appropriate Apache License headers, and I didn't find any binaries in the RC. Alan. On Wed, Apr 24, 2019 at 1:37 PM Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > Dear all, > > The source release 0.32.0 RC2 for Apache Superset is baked and available > at: > https://dist.apache.org/repos/dist/dev/incubator/superset/, public > keys are available > at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS > > This is the second ASF release candidate of Superset (!)* We're still > ironing out our release process, so please bear with us and help if you > can* > . > > Here's link to original successful VOTE thread on dev@: > > http://mail-archives.apache.org/mod_mbox/superset-dev/201904.mbox/%3ccah7q75ip1lzq61+6yvfoqvb2nser8vhsa5rca87uzrrbpj9...@mail.gmail.com%3E > > As I went along, I documented the process in RELEASING.md in the repo, > latest edits here https://github.com/apache/incubator-superset/pull/7329 > > For context (and similarly to 0.31) the `0.32` release branch was cut at > SHA 1fece0d2f, that was merged on master on Jan 22nd. From that common > ancestor, the following list of commit was added as cherry-picks. The SHAs > in the list bellow reference the cherries on the release branch, PR number > are available to get more details. > > New commits since 0.32.0rc1 *in bold:* > > *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2* > *3e6f6848 Add disclaimer and remove counter (#6738)* > c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1 > b89cdbdc RELEASING.md from master > 0e23f2e6 Add sign.sh > 21804346 [load_examples] download data at runtime (#7314) > b32d5900 Remove LICENSE entry around dataset (#7318) > b3aa5633 (release--0.31) 0.31rc23 > 24a595f4 bugfix: improve 'Time Table' (#6959) > c70abbed 0.31rc22 > dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244) > 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198) > (#7242) > a9d54894 0.31.0rc21 > b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message modal > (#7179) > 2da9613f Update __init__.py (#7166) > 538da2e3 0.31.0.rc20 > 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145) > 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144) > daf2b8e5 Bump python lib croniter to an existing version (#7132) > eb4c1355 Use metric name instead of metric in filter box (#7106) > 2ff721ae handle null column_name in sqla and druid models > e83a07d3 [forms] Fix handling of NULLs > 76d26f37 0.31.0.rc19 > fe78b4ec Fix filter_box migration PR #6523 (#7066) > c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined query > (#7029) > b64a452a [sql lab] improve table name detection in free form SQL (#6793) > 2357c4aa Adding custom control overrides (#6956) > 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963) > 5d8dd142 [csv-upload] Fixing message encoding (#6971) > f454dedd [main] Disable resetting main DB attributes (#6845) > e967b268 [sqla] Fixing order-by for non-inner-joins (#6862) > a5d9a4e0 Adding template_params to datasource editor for sqla tables > (#6869) > 6b895413 [datasource] Ensuring consistent behavior of datasource > editing/saving. (#7037) > 8ef2789f Adding warning message for sqllab save query (#7028) > 0ebdb564 fix inaccurate data calculation with adata rolling and > contribution (#7035) > b3af6a26 [fix] explore chart from dashboard missed slice title (#7046) > c54b067c [db-engine-spec] Aligning Hive/Presto partition logic (#7007) > bd65942e Changing time table viz to pass formatTime a date (#7020) > 50accda9 [fix] Cursor jumping when editing chart and dashboard titles > (#7038) > 5ace5769 0.31.0rc17 > 927a5846 [WIP] fix user specified JSON metadata not updating dashboard on > refresh (#7027) > fafb824d 0.31.0rc16 > 7b72985e [fix] /superset/slice/id url is too long (#6989) > b497d9e7 fix dashboard links in welcome page (#6756) > c42afa11 0.31.0rc15 > 35c55278 Enhancement of query context and object. (#6962) > 1c41020c Split tags migration (#7002) > ec7a0b22 0.31.0rc14 > 4655cb4c Remove Cypress from package.json (#6912) > fb8e3208 0.31.0rc13 > b4cbe13d VIZ-190 fix (#6958) > 5b7b22fd 0.31.0rc12 > 51804229 Fix deck.gl form data (#6953) > 9939a52d 0.31.0rc11 > c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix > rendering regression from the introduction of bignumber (#6937) > 9940d30a 0.31.0rc10 > 3df2b8d5 Add a safety check before getting clientHeight (#6923) > ccb51385 v0.31.0rc9 > db0235fb Fix database typeahead in SQL Lab (#6917) > 953d6dc9 Address tooltip's disappearance and stickiness (#6898) > c0eaa5f6 Fix extra_filters in multi line viz (#6868) > ebcadc1f (apache/cherry_ebcadc1f50994d98bd3dc42e2199b8d0328c061c) Fix > tooltip (#6895) > 5fa5acb5 Add show metadata button back to the explore view (#6911) > ce76560a v0.31.0rc8 > 8c549b46 Relayout SQL Editor (#6872) > bfe18963
[VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2
Dear all, The source release 0.32.0 RC2 for Apache Superset is baked and available at: https://dist.apache.org/repos/dist/dev/incubator/superset/, public keys are available at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS This is the second ASF release candidate of Superset (!)* We're still ironing out our release process, so please bear with us and help if you can* . Here's link to original successful VOTE thread on dev@: http://mail-archives.apache.org/mod_mbox/superset-dev/201904.mbox/%3ccah7q75ip1lzq61+6yvfoqvb2nser8vhsa5rca87uzrrbpj9...@mail.gmail.com%3E As I went along, I documented the process in RELEASING.md in the repo, latest edits here https://github.com/apache/incubator-superset/pull/7329 For context (and similarly to 0.31) the `0.32` release branch was cut at SHA 1fece0d2f, that was merged on master on Jan 22nd. From that common ancestor, the following list of commit was added as cherry-picks. The SHAs in the list bellow reference the cherries on the release branch, PR number are available to get more details. New commits since 0.32.0rc1 *in bold:* *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2* *3e6f6848 Add disclaimer and remove counter (#6738)* c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1 b89cdbdc RELEASING.md from master 0e23f2e6 Add sign.sh 21804346 [load_examples] download data at runtime (#7314) b32d5900 Remove LICENSE entry around dataset (#7318) b3aa5633 (release--0.31) 0.31rc23 24a595f4 bugfix: improve 'Time Table' (#6959) c70abbed 0.31rc22 dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244) 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198) (#7242) a9d54894 0.31.0rc21 b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message modal (#7179) 2da9613f Update __init__.py (#7166) 538da2e3 0.31.0.rc20 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145) 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144) daf2b8e5 Bump python lib croniter to an existing version (#7132) eb4c1355 Use metric name instead of metric in filter box (#7106) 2ff721ae handle null column_name in sqla and druid models e83a07d3 [forms] Fix handling of NULLs 76d26f37 0.31.0.rc19 fe78b4ec Fix filter_box migration PR #6523 (#7066) c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined query (#7029) b64a452a [sql lab] improve table name detection in free form SQL (#6793) 2357c4aa Adding custom control overrides (#6956) 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963) 5d8dd142 [csv-upload] Fixing message encoding (#6971) f454dedd [main] Disable resetting main DB attributes (#6845) e967b268 [sqla] Fixing order-by for non-inner-joins (#6862) a5d9a4e0 Adding template_params to datasource editor for sqla tables (#6869) 6b895413 [datasource] Ensuring consistent behavior of datasource editing/saving. (#7037) 8ef2789f Adding warning message for sqllab save query (#7028) 0ebdb564 fix inaccurate data calculation with adata rolling and contribution (#7035) b3af6a26 [fix] explore chart from dashboard missed slice title (#7046) c54b067c [db-engine-spec] Aligning Hive/Presto partition logic (#7007) bd65942e Changing time table viz to pass formatTime a date (#7020) 50accda9 [fix] Cursor jumping when editing chart and dashboard titles (#7038) 5ace5769 0.31.0rc17 927a5846 [WIP] fix user specified JSON metadata not updating dashboard on refresh (#7027) fafb824d 0.31.0rc16 7b72985e [fix] /superset/slice/id url is too long (#6989) b497d9e7 fix dashboard links in welcome page (#6756) c42afa11 0.31.0rc15 35c55278 Enhancement of query context and object. (#6962) 1c41020c Split tags migration (#7002) ec7a0b22 0.31.0rc14 4655cb4c Remove Cypress from package.json (#6912) fb8e3208 0.31.0rc13 b4cbe13d VIZ-190 fix (#6958) 5b7b22fd 0.31.0rc12 51804229 Fix deck.gl form data (#6953) 9939a52d 0.31.0rc11 c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix rendering regression from the introduction of bignumber (#6937) 9940d30a 0.31.0rc10 3df2b8d5 Add a safety check before getting clientHeight (#6923) ccb51385 v0.31.0rc9 db0235fb Fix database typeahead in SQL Lab (#6917) 953d6dc9 Address tooltip's disappearance and stickiness (#6898) c0eaa5f6 Fix extra_filters in multi line viz (#6868) ebcadc1f (apache/cherry_ebcadc1f50994d98bd3dc42e2199b8d0328c061c) Fix tooltip (#6895) 5fa5acb5 Add show metadata button back to the explore view (#6911) ce76560a v0.31.0rc8 8c549b46 Relayout SQL Editor (#6872) bfe18963 [cosmetic] TableSelector use instead of for refresh (#6783) 19b588b5 0.31.0rc7 d7e038ea Fixing issue where tooltip gets hidden on dashboard for all charts (#6852) 38e0ddac 0.31.0rc6 b7d2bd09 Fix line chart overflowing the right side (#6829) b7e02ab7 [sql lab] fix stuck offline (#6782) 8a7c245c 0.31.0rc5 f24efa72 Backend only tagging system (#6823) 1ddacc42 [wtforms] Using wtforms-json which supports None (#5445) 4f37b9ae 0.31.0rc4 845c7aa9 creating new circular-json safe stringify and replacing one
