Docs are versioned here:
https://readthedocs.org/projects/apache-superset/

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://github.com/apache/incubator-superset/tree/master/RELEASING

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://github.com/apache/incubator-superset/issues/8795#issuecomment-565769648
>
> 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.
>
> ---------------------------------------------------------------------
>

Reply via email to