-
Notifications
You must be signed in to change notification settings - Fork 13
2.8x, 2.9x and higher 2.77 core
September 23, 2016
https://trac.transmissionbt.com/ticket/6168#comment:1
Official trac and svn are a bit in disarray with a full or partial move to github pending. I will continue to monitor official (trac, svn, github, etc.) issues, changes and source for any pertinence to the 2.77 core and resolve such.
2.77 core
May 6, 2016 — Official 2.9x branch remains as described below per 2.8×.
And for those reasons cfpp2p fork of transmission will not be utilizing
2.8x, 2.9x or higher.
NONE of the 2.8x branch’s current unsolved or past bugs have
ever been introduced to these repositories. Using the 2.77 core,
all 2.8x features and enhancements are included in these commits (except rename).
Note that it was decided to maintain and compile the choice 2.7x core
rather than the somewhat buggy 2.8x core. That is why you will see
only infrequent and far less bug fixes than the official 2.8x branches.
Simply stated, 2.7x core is extremely stable and reliable. You won’t
have to worry about running it for extended days and having it quit
on you unexpectedly.
The included remote GUI port is fine tuned to the daemon released here.
https://github.com/cfpp2p/transmission/commits/svn/trunk
https://github.com/cfpp2p/transmission/commits/cygwin
https://github.com/cfpp2p/transmission/commits/Windows_Daemon_%26_Clients
The February 8, 2014 release already included the updates to the DHT and fixed an insignificant
memory leak after adding a corrupt torrent.
(Yet to be fixed in the official 2.8x branch). June-06-2014
A multitude of new bugs were introduced with the official 2.8x branch’s
quark and threading model changes. The official 2.8x branch’s quark and
threading model changes introduced and continue to allow for a multitude
of unsolved past and yet undiscovered new bugs and crashes.
This repository utilizes the well respected 2.77 core.