GitHub user manimovassagh added a comment to the discussion: Please release 6.1.0 or at least 6.0.1
I feel your pain. 6.0.0 was rough around the edges and it's frustrating to be stuck on it when you can see the fixes sitting in RC branches. A few things that might help while you wait: 1. **Pin specific bug-fix commits** -- If your IT admin won't run an RC, you can cherry-pick individual fix commits from the `6.0.1rc` or `master` branch into your 6.0.0 deployment. Build from source with just the fixes you need: ```bash git clone https://github.com/apache/superset.git git checkout 6.0.0 git cherry-pick <commit-hash> # repeat for each fix docker build -t superset-patched . ``` This keeps you on an "official" base while addressing the worst issues. 2. **Run from the RC tag directly** -- The RC images are published to Docker Hub. If your admin's concern is about stability rather than policy, point out that RCs are feature-frozen and only contain bug fixes on top of the last release. `apache/superset:6.1.0rc1` is significantly more stable than `6.0.0` for day-to-day use. 3. **Track the release timeline** -- Release discussions and votes happen on the [[email protected]](https://lists.apache.org/[email protected]) mailing list. That's where you'll see the vote threads for 6.0.1 or 6.1.0 GA. Subscribing there gives you a heads-up before the official announcement. The Apache release process requires a formal vote from committers, which is why RCs can sit for a while. But the fixes are real and tested -- the RC label is more about governance than quality. GitHub link: https://github.com/apache/superset/discussions/38654#discussioncomment-16233546 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
