Overseerr Development Status

[sct]

Hello everyone! I know it's been a long time since the last update. The team has had a lot of real-life obligations to take care of. It's hard to find free time to dedicate to Overseerr right now. That doesn’t mean it’s abandoned or we don’t care about it. It’s still software we care very deeply about.

We are still looking at PRs when we can and merging what we can. Active development is very, very slow, but it also happens whenever we find the time. We have always required a very strict level of quality in our contributions to ensure Overseerr is as bug-free as possible. That means some of the pending larger pull requests are very hard for us to review right now. There is a reason that even though the last stable release was a year ago, things run so well!

It’s also not easy to bring in new, active team members without extensive proof of the person’s quality of contribution. The team we have today was born out of piles of contributions to Overseerr, and they have proven themselves capable of maintaining the quality standards that Overseerr generally has.

So, no, Overseerr is not dead. It’s just partially paused while the team continues to work out real-life obligations.

[alexsalex]

Could you take a look at this: #1638
Thank you!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[KJThaDon]

Still no new update?

[Eunanibus]

I think the team might be cornering themselves in here.

Team is too busy with obligations to vet contributions

Without contributions, aspiring contributors can't prove their quality.

Without contributions being accepted, development crawls.

Is there maybe a plan of action or an onboarding process to maybe widen the circle of core contributors that can support the team?

[gshpychka]

Could you release a new version in the meantime (create a release from the current code)?

[modem7]

Could you release a new version in the meantime (create a release from the current code)?

That's what the dev tag is for atm.

[Erwan-loot]

We are discussing a true release, not just a tag we have to follow. We want to know what the changes are without having to read every PR and commit. This thread exists because we haven't had a release in more than a year, so in terms of code development, it seems abandoned.

[sct]

I have been going through PRs and trying to get things merged. We can have a new release in a week or two. I want to merge a few more PRs before we do so. Some of them have significant changes and need some time to be tested before we release them on the stable branch.