The security docs for both the latest version and the official ASF release attempt to document how to add a datasource for a gamma user: https://apache-superset.readthedocs.io/en/0.35.1/security.html#managing-gamma-per-data-source-access https://apache-superset.readthedocs.io/en/latest/security.html#managing-gamma-per-data-source-access
But both docs show this screen: https://apache-superset.readthedocs.io/en/latest/_images/create_role.png And in my official ASF version of Superset the screen looks like the attached. -----Original Message----- From: Maxime Beauchemin <maximebeauche...@gmail.com> Sent: Monday, December 16, 2019 4:47 PM To: dev@superset.incubator.apache.org Cc: d...@superset.apache.org Subject: [EXTERNAL] Re: Stability of git master branch vs. PyPI release Docs are versioned here: https://urldefense.proofpoint.com/v2/url?u=https-3A__readthedocs.org_projects_apache-2Dsuperset_&d=DwIBaQ&c=1hIq-C3ayh4zm6RZ7m4R2A&r=YFv754w0-1hOQn5jCB3GpLIc7nupwqAk7x9jHnHpUVw&m=xYwKG1L4QR342Tl67FNlfkN2ip5W7yWW_3JjhSfFUtM&s=sR61BjxKSe1prHJmSka5FDtsiuUv-vhYqBGXBI_JZLk&e= But you're right, superset.apache.org *should* point to latest official ASF release (and it does not, my mistake) All SHAs on master pass the test suite, but ASF releases also guarantee: * a vote has to pass with PPMC members, sometimes multiple release candidates are voted-on prior to publishing a release * more rigor around license validation * pinned documentation in the link above * a signed tarball on SVN * a process for patch/micro releases on top of that release * [eventually] and official docker / tag * ... maybe more ... (?) There's a Slack channel #apache-releases dedicated to people coordinating on releases if you want to follow what is going on or get involved. Find more about the release process here: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dsuperset_tree_master_RELEASING&d=DwIBaQ&c=1hIq-C3ayh4zm6RZ7m4R2A&r=YFv754w0-1hOQn5jCB3GpLIc7nupwqAk7x9jHnHpUVw&m=xYwKG1L4QR342Tl67FNlfkN2ip5W7yWW_3JjhSfFUtM&s=htfVjyB-OFWqLs4fBSySsnhV1LaiAYiCx9Y50svzPt8&e= Max On Mon, Dec 16, 2019 at 11:20 AM Brannon, Terrence <terrence.bran...@usbank.com.invalid> wrote: > I'm not sure if this is the right place to ask this, but: > > 0.35.1 version of Superset was released to PyPI on Nov 26, 2019. > > Since then there have been about 100 new commits to master. > > It is also a fact that the online docs are sync'ed to the master > branch NOT the PyPI release: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache > _incubator-2Dsuperset_issues_8795-23issuecomment-2D565769648&d=DwIBaQ& > c=1hIq-C3ayh4zm6RZ7m4R2A&r=YFv754w0-1hOQn5jCB3GpLIc7nupwqAk7x9jHnHpUVw > &m=xYwKG1L4QR342Tl67FNlfkN2ip5W7yWW_3JjhSfFUtM&s=gh6G8erbPyPB94hCGOM_4 > TSbHDMzd0sdP_6YwWdnBs0&e= > > This of course makes one wonder: which version of Superset is most stable? > Do both pass a test suite? If so then the git version would be more > attractive because it has more features and fixes. > > - T > > > > U.S. BANCORP made the following annotations > --------------------------------------------------------------------- > Electronic Privacy Notice. This e-mail, and any attachments, contains > information that is, or may be, covered by electronic communications > privacy laws, and is also confidential and proprietary in nature. If > you are not the intended recipient, please be advised that you are > legally prohibited from retaining, using, copying, distributing, or > otherwise disclosing this information in any manner. Instead, please > reply to the sender that you have received this communication in > error, and then immediately delete it. Thank you in advance for your > cooperation. > > --------------------------------------------------------------------- > U.S. BANCORP made the following annotations --------------------------------------------------------------------- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ---------------------------------------------------------------------
