Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NEW VERSION] Superset 2.0.1, 2.1.0 #237

Closed
2 tasks done
Tracked by #374 ...
fhennig opened this issue Jul 25, 2022 · 13 comments · Fixed by stackabletech/docker-images#216
Closed
2 tasks done
Tracked by #374 ...

[NEW VERSION] Superset 2.0.1, 2.1.0 #237

fhennig opened this issue Jul 25, 2022 · 13 comments · Fixed by stackabletech/docker-images#216
Assignees

Comments

@fhennig
Copy link
Contributor

fhennig commented Jul 25, 2022

Which new version of Apache Superset should we support?

New major version 2.0

Additional information

See the changelog, the release notes and breaking changes.

Changes / Additions

In the scope of this ticket:

  • check that tests, getting started scripts, documentation and demos work with the new version. Many of the changes are UI-based, so screenshots should be checked for accuracy.
  • have a look at the items below from the release notes and create new issues for things which merit further work
  • as many changes are UI-based it may be worth showcasing some new UI features in our demos

2.0.1 is not released as of the time of this writing but the release vote is ongoing: https://lists.apache.org/thread/vjhnxw1yrd3wo356c0pgljv9nn7trmyv

From the release notes:-

  • 2.0.0
    • resource limits (check these against our defaults?): 20052
    • switch from sqlalchemy-trino to trino-python-client: 19957
    • min. python version is now 3.8: 19017
  • 1.5.2
    • (only minor fixes)

Implementation checklist

Please don't change anything in this list.
Not all of these steps are necessary for all versions.

TODO

@maltesander
Copy link
Member

Do we already want to do this or wait for a 2.0 patch release @lfrancke ?

@lfrancke
Copy link
Member

lfrancke commented Oct 3, 2022

Good question: @siegfriedweber @fhennig @soenkeliebau
Any opinions? Usually I'd prefer for us to not jump on a new major version immediately but if you think it's worth it I'm happy to...

@adwk67
Copy link
Member

adwk67 commented Oct 4, 2022

I think it makes sense doing a refinement on this, if only to list the main changes up to 2.0.0. We can always put it back in the "waiting for" column if we decide to wait for 2.x.

@adwk67 adwk67 self-assigned this Oct 4, 2022
@lfrancke lfrancke changed the title [NEW VERSION] Superset 2.0.0 [NEW VERSION] Superset 2.0.1 Oct 7, 2022
@lfrancke lfrancke self-assigned this Oct 7, 2022
@sbernauer sbernauer assigned sbernauer and unassigned lfrancke and adwk67 Oct 13, 2022
@lfrancke
Copy link
Member

A new vote on 2.0.1 has been started: https://lists.apache.org/thread/7whg78bdc7pn1rxl64o0f3bhprrdf72k

@lfrancke
Copy link
Member

The new vote has received another -1 which might fail the release.
I don't feel too confident about supporting Superset 2.0 right now.
I will remove it from this release and we can try again next release.

@sbernauer
Copy link
Member

Ok for me

@sbernauer
Copy link
Member

@lfrancke
Copy link
Member

lfrancke commented Nov 2, 2022

No, that is the result of the new vote and it failed again :)

@sbernauer
Copy link
Member

Ah sry 🤦

@sbernauer
Copy link
Member

They finally did it...

@maltesander
Copy link
Member

one task left, not sure why it closed!

@maltesander maltesander reopened this Apr 25, 2023
@bors bors bot closed this as completed in 8ef9133 Apr 26, 2023
@soenkeliebau
Copy link
Member

Needs input from @lfrancke on whether both versions should be released or just 2.1.0

@lfrancke
Copy link
Member

lfrancke commented May 5, 2023

I think only 2.1.0 is required.
Any other opinions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment