[suggestion] Change the versioning scheme of qBittorrent.

Bug #712489 reported by Mith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qBittorrent
New
Undecided
Unassigned

Bug Description

Main reason i post this is because of the following link, i hope in the future this can be changed: http://forums.bakabt.com/index.php?topic=19469.msg4562861#msg4562861

"Quote from: dart8 on January 13, 2011, 12:46:48 PM
I understand it is annoying to update list every day ... And there is some mysterious reason why 2.6X or 2.5X can not be added, while all other clients (except Utorrent which is most popular and important) have more liberal rules.
When I said there were technical reasons, I meant it - there's no conspiracy here."

The issue is in the versioning scheme that the qBittorrent developers use. 2.5.0.0 indicates the stable 2.5.0 release, while 2.5.0.1 indicates the 2.5.0 RC1, and so on. Therefore, if we only wish to allow stable releases (which we do), we cannot whitelist the entire 2.5.x series (since the tracker can't handle listings of the form 2.5.x.0).

Go complain to the qBittorrent development team if you want the 2.6.x series whitelisted.

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

I heard about this already. However, I'm still waiting on a better alternative versioning scheme.

+ trackers could just allow v2.5.x.x
Why do they care if the qBittorrent (a GUI) is not a stable release since only libtorrent-rasterbar (the backend library used by qBittorrent) interacts with the trackers and we only use stable libtorrent releases? I don't see how a bug in qBittorrent GUI can have any negative effect on the trackers.

I already sent a Private message to the BakaBT admin about this, several weeks ago but he did not reply.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.