You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/05/27 08:29:15 UTC

[GitHub] [superset] villebro opened a new pull request, #20210: docs: update release instructions

villebro opened a new pull request, #20210:
URL: https://github.com/apache/superset/pull/20210

   ### SUMMARY
   
   Add more detailed steps to release documentation, specifically relating to cherry picking.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   <!--- Skip this if not applicable -->
   
   ### TESTING INSTRUCTIONS
   <!--- Required! What steps can be taken to manually verify the changes? -->
   
   ### ADDITIONAL INFORMATION
   <!--- Check any relevant boxes with "x" -->
   <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] villebro commented on a diff in pull request #20210: docs: update release instructions

Posted by GitBox <gi...@apache.org>.
villebro commented on code in PR #20210:
URL: https://github.com/apache/superset/pull/20210#discussion_r883549091


##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the
+`CHANGELOG.md` file in the root of the repo. Remember to also make sure to update the branch id (with the above command
+`1.5` needs to be changed to `1.5.0`)
 
 Then, in `UPDATING.md`, a file that contains a list of notifications around
 deprecations and upgrading-related topics,
 make sure to move the content now under the `Next Version` section under a new
 section for the new release.
 
+#### Patch release (e.g. 1.5.1)
+
+To compare the forthcoming patch release with the latest release from the same branch, et the previous

Review Comment:
   🤣 🤣 🤣 



-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] michael-s-molina commented on a diff in pull request #20210: docs: update release instructions

Posted by GitBox <gi...@apache.org>.
michael-s-molina commented on code in PR #20210:
URL: https://github.com/apache/superset/pull/20210#discussion_r883534178


##########
RELEASING/README.md:
##########
@@ -67,6 +67,33 @@ need to be done at every release.
     svn update
 ```
 
+To minimize risk of mixing up your local development environment, it's recommended to work on the

Review Comment:
   ```suggestion
   To minimize the risk of mixing up your local development environment, it's recommended to work on the
   ```



##########
RELEASING/README.md:
##########
@@ -67,6 +67,33 @@ need to be done at every release.
     svn update
 ```
 
+To minimize risk of mixing up your local development environment, it's recommended to work on the
+release in a different directory than where the devenv is located. In this example we'll clone

Review Comment:
   ```suggestion
   release in a different directory than where the devenv is located. In this example, we'll clone
   ```



##########
RELEASING/README.md:
##########
@@ -67,6 +67,33 @@ need to be done at every release.
     svn update
 ```
 
+To minimize risk of mixing up your local development environment, it's recommended to work on the
+release in a different directory than where the devenv is located. In this example we'll clone
+the repo directly from the main `apache/superset` repo to a new directory `superset-release`:
+
+```bash
+cd <MY PROJECTS PATH>
+git clone git@github.com:apache/superset.git superset-release
+cd superset-release
+```
+
+We recommend setting up a virtual environment to isolate the python dependencies from your main
+setup:
+
+```bash
+virtualenv venv
+source venv/bin/activate
+```
+
+
+In addition, we recommend using the [`cherrytree`](https://pypi.org/project/cherrytree/) tool for
+automating cherrypicking, as it will help speed up the release process. To install `cherrytree`

Review Comment:
   ```suggestion
   automating cherry picking, as it will help speed up the release process. To install `cherrytree`
   ```



##########
RELEASING/README.md:
##########
@@ -116,23 +147,101 @@ a branch named with the release MAJOR.MINOR version (on this example 0.37).
 This new branch will hold all PATCH and release candidates
 that belong to the MAJOR.MINOR version.
 
+### Creating an initial minor release (e.g. 1.5.0)
+
 The MAJOR.MINOR branch is normally a "cut" from a specific point in time from the master branch.
-Then (if needed) apply all cherries that will make the PATCH.
+When creating the initial minor release (e.g. 1.5.0), create a new branch:
+```bash
+git checkout master
+git pull
+git checkout -b ${SUPERSET_GITHUB_BRANCH}
+git push origin $SUPERSET_GITHUB_BRANCH
+```
+
+Note that this initializes a new "release cut", and is NOT needed when creating a patch release
+(e.g. 1.5.1).
+
+### Creating a patch release (e.g. 1.5.1)
+
+When getting ready to bake a patch release, simply checkout the relevant branch:
 
 ```bash
-git checkout -b $SUPERSET_GITHUB_BRANCH
-git push upstream $SUPERSET_GITHUB_BRANCH
+git checkout master
+git pull
+git checkout ${SUPERSET_GITHUB_BRANCH}
 ```
 
+### Cherrypicking

Review Comment:
   ```suggestion
   ### Cherry picking
   ```



##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the
+`CHANGELOG.md` file in the root of the repo. Remember to also make sure to update the branch id (with the above command
+`1.5` needs to be changed to `1.5.0`)
 
 Then, in `UPDATING.md`, a file that contains a list of notifications around
 deprecations and upgrading-related topics,
 make sure to move the content now under the `Next Version` section under a new
 section for the new release.
 
+#### Patch release (e.g. 1.5.1)
+
+To compare the forthcoming patch release with the latest release from the same branch, et the previous
+version as the tag of the previous release (in this example `1.5.0`; remember to update accordingly)

Review Comment:
   ```suggestion
   version as the tag of the previous release (in this example `1.5.0`; remember to update it accordingly)
   ```



##########
RELEASING/README.md:
##########
@@ -116,23 +147,101 @@ a branch named with the release MAJOR.MINOR version (on this example 0.37).
 This new branch will hold all PATCH and release candidates
 that belong to the MAJOR.MINOR version.
 
+### Creating an initial minor release (e.g. 1.5.0)
+
 The MAJOR.MINOR branch is normally a "cut" from a specific point in time from the master branch.
-Then (if needed) apply all cherries that will make the PATCH.
+When creating the initial minor release (e.g. 1.5.0), create a new branch:
+```bash
+git checkout master
+git pull
+git checkout -b ${SUPERSET_GITHUB_BRANCH}
+git push origin $SUPERSET_GITHUB_BRANCH
+```
+
+Note that this initializes a new "release cut", and is NOT needed when creating a patch release
+(e.g. 1.5.1).
+
+### Creating a patch release (e.g. 1.5.1)
+
+When getting ready to bake a patch release, simply checkout the relevant branch:
 
 ```bash
-git checkout -b $SUPERSET_GITHUB_BRANCH
-git push upstream $SUPERSET_GITHUB_BRANCH
+git checkout master
+git pull
+git checkout ${SUPERSET_GITHUB_BRANCH}
 ```
 
+### Cherrypicking
+
+It is customary to label PRs that have been introduced after the cut with the label
+`v<MAJOR>.<MINOR>`. For example, for any PRs that should be included in the 1.5 branch, the
+label `v1.5` should be added.
+
+To see how well the labelled PRs would apply to the current branch, run the following command:
+
+```bash
+cherrytree bake -r apache/superset -m master -l v${SUPERSET_GITHUB_BRANCH} ${SUPERSET_GITHUB_BRANCH}
+```
+
+This requires the presence of an environment variable `GITHUB_TOKEN`. Alternatively,
+you can pass the token directly via the `--access-token` parameter (`-at` for short).
+
+#### Happy path: no conflicts
+
+This will show how many cherries will apply cleanly. If there are no conflicts, you can simply apply all cherries
+by adding the `--no-dry-run` flag (`-nd` for short):
+
+```bash
+cherrytree bake -r apache/superset -m master -l v${SUPERSET_GITHUB_BRANCH} -nd ${SUPERSET_GITHUB_BRANCH}
+```
+
+
+#### Resolving conflicts
+
+If there are conflicts, you can issue the following command to apply all cherries up until the conflict automatically, and then
+break by adding the `-error-mode break` flag (`-e break` for short):
+
+```bash
+cherrytree bake -r apache/superset -m master -l v${SUPERSET_GITHUB_BRANCH} -nd -e break ${SUPERSET_GITHUB_BRANCH}
+```
+
+After applying the cleanly merged cherries, `cherrytree` will specify the SHA of the conflicted cherry. To resolve the conflict,
+simply issue the following command:
+
+```bash
+git cherry-pick <SHA>
+```
+
+Then fix all conflicts, followed by
+
+```bash
+git add -u  # add all changes
+git cherry-pick --continue
+```
+
+After this, rerun all the above steps until all cherries have been picked, finally pushing all new commits to the release branch
+on the main repo:
+
+```bash
+git push
+```
+
+### Updating changelog
+
 Next, update the `CHANGELOG.md` with all the changes that are included in the release.
-Make sure the branch has been pushed to `upstream` to ensure the changelog generator
+Make sure the branch has been pushed to `origin` to ensure the changelog generator
 can pick up changes since the previous release.
-Change log script requires a github token and will try to use your env var GITHUB_TOKEN.
-you can also pass the token using the parameter `--access_token`.
+Similar to `cherrytree`, the change log script requires a github token, either as an env var
+(`GITHUB_TOKEN`) or as the parameter `--access_token`.
+
+#### Initial release (e.g. 1.5.0)
+
+When generating the changelog for an initial minor relese, you should compare with
+the previous release (in the example the previous release branch is `1.4`, so remember to
+update accordingly):

Review Comment:
   ```suggestion
   update it accordingly):
   ```



##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the

Review Comment:
   ```suggestion
   The script will checkout both branches, compare all the PRs, and output the lines that are needed to be added to the
   ```



##########
RELEASING/README.md:
##########
@@ -116,23 +147,101 @@ a branch named with the release MAJOR.MINOR version (on this example 0.37).
 This new branch will hold all PATCH and release candidates
 that belong to the MAJOR.MINOR version.
 
+### Creating an initial minor release (e.g. 1.5.0)
+
 The MAJOR.MINOR branch is normally a "cut" from a specific point in time from the master branch.
-Then (if needed) apply all cherries that will make the PATCH.
+When creating the initial minor release (e.g. 1.5.0), create a new branch:
+```bash
+git checkout master
+git pull
+git checkout -b ${SUPERSET_GITHUB_BRANCH}
+git push origin $SUPERSET_GITHUB_BRANCH
+```
+
+Note that this initializes a new "release cut", and is NOT needed when creating a patch release
+(e.g. 1.5.1).
+
+### Creating a patch release (e.g. 1.5.1)
+
+When getting ready to bake a patch release, simply checkout the relevant branch:
 
 ```bash
-git checkout -b $SUPERSET_GITHUB_BRANCH
-git push upstream $SUPERSET_GITHUB_BRANCH
+git checkout master
+git pull
+git checkout ${SUPERSET_GITHUB_BRANCH}
 ```
 
+### Cherrypicking
+
+It is customary to label PRs that have been introduced after the cut with the label
+`v<MAJOR>.<MINOR>`. For example, for any PRs that should be included in the 1.5 branch, the
+label `v1.5` should be added.
+
+To see how well the labelled PRs would apply to the current branch, run the following command:
+
+```bash
+cherrytree bake -r apache/superset -m master -l v${SUPERSET_GITHUB_BRANCH} ${SUPERSET_GITHUB_BRANCH}
+```
+
+This requires the presence of an environment variable `GITHUB_TOKEN`. Alternatively,
+you can pass the token directly via the `--access-token` parameter (`-at` for short).
+
+#### Happy path: no conflicts
+
+This will show how many cherries will apply cleanly. If there are no conflicts, you can simply apply all cherries
+by adding the `--no-dry-run` flag (`-nd` for short):
+
+```bash
+cherrytree bake -r apache/superset -m master -l v${SUPERSET_GITHUB_BRANCH} -nd ${SUPERSET_GITHUB_BRANCH}
+```
+
+
+#### Resolving conflicts
+
+If there are conflicts, you can issue the following command to apply all cherries up until the conflict automatically, and then
+break by adding the `-error-mode break` flag (`-e break` for short):
+
+```bash
+cherrytree bake -r apache/superset -m master -l v${SUPERSET_GITHUB_BRANCH} -nd -e break ${SUPERSET_GITHUB_BRANCH}
+```
+
+After applying the cleanly merged cherries, `cherrytree` will specify the SHA of the conflicted cherry. To resolve the conflict,
+simply issue the following command:
+
+```bash
+git cherry-pick <SHA>
+```
+
+Then fix all conflicts, followed by
+
+```bash
+git add -u  # add all changes
+git cherry-pick --continue
+```
+
+After this, rerun all the above steps until all cherries have been picked, finally pushing all new commits to the release branch
+on the main repo:
+
+```bash
+git push
+```
+
+### Updating changelog
+
 Next, update the `CHANGELOG.md` with all the changes that are included in the release.
-Make sure the branch has been pushed to `upstream` to ensure the changelog generator
+Make sure the branch has been pushed to `origin` to ensure the changelog generator
 can pick up changes since the previous release.
-Change log script requires a github token and will try to use your env var GITHUB_TOKEN.
-you can also pass the token using the parameter `--access_token`.
+Similar to `cherrytree`, the change log script requires a github token, either as an env var
+(`GITHUB_TOKEN`) or as the parameter `--access_token`.
+
+#### Initial release (e.g. 1.5.0)
+
+When generating the changelog for an initial minor relese, you should compare with
+the previous release (in the example the previous release branch is `1.4`, so remember to

Review Comment:
   ```suggestion
   the previous release (in the example, the previous release branch is `1.4`, so remember to
   ```



##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the
+`CHANGELOG.md` file in the root of the repo. Remember to also make sure to update the branch id (with the above command
+`1.5` needs to be changed to `1.5.0`)
 
 Then, in `UPDATING.md`, a file that contains a list of notifications around
 deprecations and upgrading-related topics,
 make sure to move the content now under the `Next Version` section under a new
 section for the new release.
 
+#### Patch release (e.g. 1.5.1)
+
+To compare the forthcoming patch release with the latest release from the same branch, et the previous

Review Comment:
   "et the previous version"?
   
   ![et-o-extraterrestre-steven-spielberg-reproducao_widelg](https://user-images.githubusercontent.com/70410625/170694025-fbc88900-e882-4b05-8172-ee0407684816.jpeg)
   



-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] rusackas commented on a diff in pull request #20210: docs: update release instructions

Posted by GitBox <gi...@apache.org>.
rusackas commented on code in PR #20210:
URL: https://github.com/apache/superset/pull/20210#discussion_r886005344


##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the
+`CHANGELOG.md` file in the root of the repo. Remember to also make sure to update the branch id (with the above command
+`1.5` needs to be changed to `1.5.0`)
 
 Then, in `UPDATING.md`, a file that contains a list of notifications around
 deprecations and upgrading-related topics,
 make sure to move the content now under the `Next Version` section under a new
 section for the new release.
 
+#### Patch release (e.g. 1.5.1)
+
+To compare the forthcoming patch release with the latest release from the same branch, et the previous

Review Comment:
   FYI, as of 1999, you can deploy et versions in pods 
   ![image](https://user-images.githubusercontent.com/812905/171253483-8a16990e-3094-483e-8d3a-ff8a08f2d4dd.png)



-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] michael-s-molina commented on a diff in pull request #20210: docs: update release instructions

Posted by GitBox <gi...@apache.org>.
michael-s-molina commented on code in PR #20210:
URL: https://github.com/apache/superset/pull/20210#discussion_r883553325


##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the
+`CHANGELOG.md` file in the root of the repo. Remember to also make sure to update the branch id (with the above command
+`1.5` needs to be changed to `1.5.0`)
 
 Then, in `UPDATING.md`, a file that contains a list of notifications around
 deprecations and upgrading-related topics,
 make sure to move the content now under the `Next Version` section under a new
 section for the new release.
 
+#### Patch release (e.g. 1.5.1)
+
+To compare the forthcoming patch release with the latest release from the same branch, et the previous

Review Comment:
   😆 😆 😆 



-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] villebro commented on a diff in pull request #20210: docs: update release instructions

Posted by GitBox <gi...@apache.org>.
villebro commented on code in PR #20210:
URL: https://github.com/apache/superset/pull/20210#discussion_r883551946


##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the
+`CHANGELOG.md` file in the root of the repo. Remember to also make sure to update the branch id (with the above command
+`1.5` needs to be changed to `1.5.0`)
 
 Then, in `UPDATING.md`, a file that contains a list of notifications around
 deprecations and upgrading-related topics,
 make sure to move the content now under the `Next Version` section under a new
 section for the new release.
 
+#### Patch release (e.g. 1.5.1)
+
+To compare the forthcoming patch release with the latest release from the same branch, et the previous

Review Comment:
   et the final version 😢 
   ![image](https://user-images.githubusercontent.com/33317356/170695795-b456aab7-9258-4d79-8f5a-a5bb70ea46fe.png)
   



-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] villebro commented on a diff in pull request #20210: docs: update release instructions

Posted by GitBox <gi...@apache.org>.
villebro commented on code in PR #20210:
URL: https://github.com/apache/superset/pull/20210#discussion_r883551946


##########
RELEASING/README.md:
##########
@@ -141,16 +250,29 @@ Example:
 python changelog.py --previous_version 0.37 --current_version 0.38 changelog --access_token {GITHUB_TOKEN} --risk
 ```
 
-The script will checkout both branches and compare all the PR's, copy the output and paste it on the `CHANGELOG.md`
+The script will checkout both branches and compare all the PR's and output the line that are needed to be added to the
+`CHANGELOG.md` file in the root of the repo. Remember to also make sure to update the branch id (with the above command
+`1.5` needs to be changed to `1.5.0`)
 
 Then, in `UPDATING.md`, a file that contains a list of notifications around
 deprecations and upgrading-related topics,
 make sure to move the content now under the `Next Version` section under a new
 section for the new release.
 
+#### Patch release (e.g. 1.5.1)
+
+To compare the forthcoming patch release with the latest release from the same branch, et the previous

Review Comment:
   "et the final version" 😢 
   
   ![image](https://user-images.githubusercontent.com/33317356/170695795-b456aab7-9258-4d79-8f5a-a5bb70ea46fe.png)
   



-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

[GitHub] [superset] villebro merged pull request #20210: docs: update release instructions

Posted by GitBox <gi...@apache.org>.
villebro merged PR #20210:
URL: https://github.com/apache/superset/pull/20210


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org