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

We REALLY need an update on the state of Sequel Pro's development... #3617

Open
JackWH opened this issue Dec 15, 2019 · 11 comments
Open

We REALLY need an update on the state of Sequel Pro's development... #3617

JackWH opened this issue Dec 15, 2019 · 11 comments

Comments

@JackWH
Copy link

@JackWH JackWH commented Dec 15, 2019

Sequel Pro is an absolutely indispensable tool for many of us. We rely on it to do our jobs. We recommend it to our friends and colleagues. We don't just use it in development — we know it can be trusted in production too. We've had confidence in Sequel Pro, stuck by the project for years, and some of us have even donated to support it.

Bearing in mind how much users love Sequel Pro, it's such a shame to see:

  • Over 1000 unresolved issues
  • Nearly 40 unmerged Pull Requests
  • No updates on the Twitter account for over 1 year
  • No new test release builds in 6 months
  • No new stable releases in nearly 4 years!

I'm well aware I can download a test build. But I'm sure I'm not the only developer who's reluctant to use unstable software against production databases.

Just look at the changelog for v1.2. These are great improvements... But nobody knows about them! The people who contributed to v1.2 may as well have not bothered, if users will never receive any updates. We may never know the number of developers who've abandoned Sequel Pro as a result of the notorious tab-closing crash, because they're simply not aware fixes are being worked on. And the sad truth is that these issues are being fixed — they're just never seeing the light of day.

Can anyone involved in this project provide an update? If it's been abandoned, fair enough — we had a great run together! But if it hasn't, please can the maintainers:

  • Release an official update to fix the tab-closing issues (first reported 18 months ago!)
  • Post an acknowledgement that the project is still being developed
  • Provide a rough estimate of when the next release is likely to be?
  • Post a tweet to let your users know the project hasn't been abandoned

It just hurts me to see issues piling up, whilst the hard work contributors make to fix these bugs goes unreleased to end-users for literally years at a time.

Apologies for the rant. I hope you realise it comes from a place of love for one of my most relied-upon developer tools ❤️

@Nezteb

This comment has been minimized.

Copy link

@Nezteb Nezteb commented Dec 18, 2019

Until the TLS 1.2 issue in #2854 is fixed, my company can't use SequelPro. We use the free edition of DBeaver as our primary SQL client now.

@MikeBeas

This comment has been minimized.

Copy link

@MikeBeas MikeBeas commented Dec 24, 2019

I have been using the nightly builds for over a year now because of the tab-closing crash but even the nightly builds now have problems on Catalina with the sidebar not being sized properly on launch. I haven't found any other DB clients I like as much as this one and I'll be sorely disappointed if it's abandoned.

I would also really like an answer about the status of this project. I heard some people were considering the idea of a fork? Is that happening?

@lagnat

This comment has been minimized.

Copy link

@lagnat lagnat commented Dec 25, 2019

@dmoagx @stuconnolly @Kaspik @stychos What's the status of this project?

@dmoagx

This comment has been minimized.

Copy link
Member

@dmoagx dmoagx commented Dec 30, 2019

@lagnat There are no secrets (at least I'm not aware of any) about the status of the project. Everything that is there to know has already been discussed in this issue tracker.

@lagnat

This comment has been minimized.

Copy link

@lagnat lagnat commented Dec 31, 2019

@dmoagx My apologies if this had already been discussed. I scanned a few pages of issues and didn't see anything, so it seemed like a reasonable question to ask. I'll dig a little deeper but if you're already aware of a status discussion thread, that would help.

@MattRiddell

This comment has been minimized.

Copy link

@MattRiddell MattRiddell commented Dec 31, 2019

Yeah I'm super keen to know too - willing to put my money where my mouth is if it helps.

Sequel Pro is by far the best MySQL DB management app!

@jpike88

This comment has been minimized.

Copy link

@jpike88 jpike88 commented Jan 6, 2020

It's a sad state of affairs and I don't expect it to improve anytime soon, this situation has been the case for years now.

I switched to TablePlus about six months ago (which has a free version) and I haven't looked back. My advice to everyone struggling with sequel pro's dysfunctional situation: stop worrying and switch to something that's actually being maintained, stable and cross-platform. This project shouldn't have any more pressure/expectation placed on it until it has clear leadership and proper release activity.

P.S. Riding on a nightly build for something as critical as a DB administration tool should be considered unacceptable and anyone doing that needs to consider what excuses they're going to give if things break in an unexpected manner.

@markcarver

This comment has been minimized.

Copy link

@markcarver markcarver commented Jan 6, 2020

This topic is getting ridiculous. Please just make a release already... it doesn't have to be 100% perfect; just mostly working and actually usable (unlike the current "stable" 1.1.2 version).

@thomscode

This comment has been minimized.

Copy link

@thomscode thomscode commented Jan 6, 2020

Without any stable releases I will probably switch to another tool once I take the time to find one I like. Until that time, I did find the most recently successful nightly build (built about 6 months ago) to resolve the issues I was having.

@nilbus

This comment has been minimized.

Copy link

@nilbus nilbus commented Jan 8, 2020

Everything that is there to know has already been discussed in this issue tracker.

If anyone can find what's being referred to here about the project status, some comment links would be helpful. Thanks!

@snebes

This comment has been minimized.

Copy link

@snebes snebes commented Jan 13, 2020

@nilbus @lagnat #3385 is the most recent thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.