Replies: 13 comments 28 replies
-
|
@sqomrzyk Beta is available currently on main site & Release Candidate will be posted in next week or two......Final........when it's ready 🤣 |
Beta Was this translation helpful? Give feedback.
-
|
Fr been using the 5.0 beta for a month now and It's been awesome. A few bugs here and there but I'm sure its almost ready for a full release. Absolutely loving the full dark mode compatibility as well! |
Beta Was this translation helpful? Give feedback.
-
Please open ticket(s) after the "RC" is released if still experiencing these bugs otherwise they may not get fixed if we haven't come across them ourselves.
There were issues with dark mode compatibility which have since been fixed (didn't make the beta), there are others in relation to the WebUI dark mode which will more thank likely miss the "RC" too |
Beta Was this translation helpful? Give feedback.
-
Or four.. ? ;-) |
Beta Was this translation helpful? Give feedback.
-
|
I want to try the beta |
Beta Was this translation helpful? Give feedback.
-
|
@xavier2k6 Is there any chance a compact view for the webui can squeeze in before release? Seems like it would be easy to address. For reference: #21031 |
Beta Was this translation helpful? Give feedback.
-
Please open an actual ticket & a web-dev can look into it. |
Beta Was this translation helpful? Give feedback.
-
|
Would love to see 5.0 start, because it's going to take months before it's vetted through the cycle. |
Beta Was this translation helpful? Give feedback.
-
Yup, Sledge's constant MIAs are well documented online. It was half a year or so at one point and they even considered setting things up for releases without him then he magically appeared again. |
Beta Was this translation helpful? Give feedback.
-
If that is the case, maybe they should actually set things up this time and make it permanent so we get timely releases no matter what. Also, why is there only 1 maintainer for such a big project used by countless numbers of people around the world? |
Beta Was this translation helpful? Give feedback.
-
|
@Pentaphon I appreciate you following me on GitHub, but if they're not around it's something for the project to determine. Based on Transmission 4.0.6 being denied globally now, qB has a more important posture than ever. 5.0 is going to be a beyond substantial release. |
Beta Was this translation helpful? Give feedback.
-
Something I think they need to sort out hopefully sooner rather than later. |
Beta Was this translation helpful? Give feedback.
-
I don't follow anybody on github. I just like to keep up with certain projects that interest me. I do think that having just 1 maintainer is a problem that Transmission doesn't currently have and qBittorrent should learn from that example as it is a much bigger project now. |
Beta Was this translation helpful? Give feedback.
-
|
I understand a new release may be overdue but trying to rush one out when there's multiple open tickets related to memory leak(s) doesn't seem wise. People have waited this long, they can surely wait a little longer for a new release that doesn't crash qb or the system itself. |
Beta Was this translation helpful? Give feedback.
-
I've been telling this project to just keep doing 4.x releases to fix major bugs but they insisted on moving to 5.0.0 and now the maintainer seems to be gone again so we have the curious problem of a complete standstill right as a new major release is about to come out. Hopefully once they get 5.0.0 out the door they can spend more time fixing bugs like the ones you mentioned but I wouldn't hold my breath. The issues page keeps ballooning and getting closer to a whopping 3,000 issues. |
Beta Was this translation helpful? Give feedback.
-
|
I'd think the priority would be making sure a new major release is stable and doesn't contain known bugs that can take down the whole system. A lot of people will be updating from older releases that work for them, who'll be in for a rude awakening when they update to 5.0.0 and it hoses their system. If it took this long for a new release, who knows how long it will take to fix when it should've been fixed before being put out?! What a horrible management decision that users will pay the price for. Sledge doesn't seem want the job, only the title. There's nothing worse than a derelict "leader". |
Beta Was this translation helpful? Give feedback.
-
They're doing just that. Bugfixes are done at the same time as new features and many get ported back, also 5.0 would likely resolve a bunch of these open issues, given how big of an update it is likely they'll close a bunch of them as they've done previously. |
Beta Was this translation helpful? Give feedback.
-
|
@sledgehammer999 any thoughts on having a 2nd maintainer for this project? |
Beta Was this translation helpful? Give feedback.
-
|
It's really a matter for the team. You won't get a response or at least the one you're after.. |
Beta Was this translation helpful? Give feedback.
-
This was already discussed along time ago & our maintainer will continue creating/releasing the official builds.
Correct |
Beta Was this translation helpful? Give feedback.
-
|
5.0 will be released when it's ready & when our maintainer is back. Next 5.0 based build will more than likely still be an RC, I wouldn't possibly expect official 5.0 until start of 2025. DISCLAIMER: This is not a definitive timeframe & subject to change!, the opinion(s) expressed here are my own. |
Beta Was this translation helpful? Give feedback.
-
|
I could be wrong as I don't know the full history but it seems the root problem is pride. You've got a "leader" who's inconsistent at best, with long periods of no contact, who refuses to step aside in favor of someone who actually wants to do the work for the betterment of the project and its users. To make it worse, this problem and the leaderships unwillingness to budge has been ongoing for years now. Maybe the solution is to fork it, drop the dead weight, and get the train moving again. The farther off course you get, the bigger the action required to correct it. Then again if anyone really wanted to go that route, there's been plenty of time to build up the courage to take the leap. It's really unfortunate for projects and users when situations like this exist. |
Beta Was this translation helpful? Give feedback.
-
@xavier2k6 what happens if the maintainer is no longer able to do his duties for whatever reason? Who does the responsibility then go to? |
Beta Was this translation helpful? Give feedback.
-
|
The 2 main devs. |
Beta Was this translation helpful? Give feedback.
-
I've explained this numerous times.......it is always a fire fighting exercise |
Beta Was this translation helpful? Give feedback.
-
Some issues have indeed been resolved via us or indeed in our upstream dependencies, I've kept some tickets open as there has been no official build that includes all of these fixes (collectively) & also we need some users to feedback if their issue is actually resolved but some users will not use beta/rc or nightly builds....will wait for official release etc. |
Beta Was this translation helpful? Give feedback.
-
|
whats the temperature of the dev team to fork so the project can prosper? Is this being discussaed somewere or is all behind the scenes? |
Beta Was this translation helpful? Give feedback.
-
Why would you fork qBittorrent when it is more popular than ever? All people want is for releases to come out sooner and all that requires is a more active maintainer or 2 maintainers who can cover each other. |
Beta Was this translation helpful? Give feedback.
-
|
The problem is that @sledgehammer999 doesn't feel responsible to users, he said - in a week, but disappeared for 3 months. Maybe something happened and that would be a valid reason, but he didn't see fit to report it. Or maybe the developers know where he disappeared to? |
Beta Was this translation helpful? Give feedback.
-
|
It's not pressing.. just disappointing, not much point in further discussion Would be nice to at least port one or two things across for a 4.7 since 5.0 is still almost half a year away though.. |
Beta Was this translation helpful? Give feedback.
-
Sounds a bit extreme. I'd say a month after RC, tops. |
Beta Was this translation helpful? Give feedback.
-
Looking at the timeline for 4.6.0 (which was a minor revision) there was 2 months for a final release from RC. https://www.qbittorrent.org/news#sun-oct-22th-2023---qbittorrent-v4.6.0-release IMO - RC should be released after Qt 6.7.3 or more preferably first release of Qt 6.8 series (both are scheduled for end of September)
v5.0 Final - should be released some time in January of 2025, perhaps coinciding with Qt 6.8.2 release.
Perhaps something like below: Start of October 2024 - RC1 - Qt 6.7.3 (~20.September.2024)/Boost 1.86.0 (out now) |
Beta Was this translation helpful? Give feedback.
-
|
Sledge is back. Hopefully the RC and 4.6.6 come out soon. I really doubt 5.0.0 will be delayed to 2025 |
Beta Was this translation helpful? Give feedback.
-
Hello!
Not asking for an exact date here but are we talking weeks, months or maybe you still dont know when it's going to release?
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions