Bump version to 2.7.1

NEWS

@@ -1,3 +1,42 @@
+BFGMiner Version 2.7.1 - August 22, 2012
+
+- Update windows build instructions courtesy of sharky.
+- Increase max curls to number of mining threads + queue * 2, accounting for up
+and downstream comms.
+- Queue enough requests to get started.
+- There is no point trying to clone_work in get_work() any more since we clone
+on every get_work_thread where possible.
+- There is no point subtracting 1 from maxq in get_work_thread.
+- miner.php allow page title to be defined in myminer.php
+- Only set lagging flag once there are no staged work items.
+- select_pool does not switch back to the primary once lagging is disabled.
+- Increment total work counter under mutex lock.
+- Increment the queued count after the curl is popped in case there's a delay
+waiting on curls and we think we've queued work when in fact we're waiting on
+curls.
+- Do the dynamic timing in opencl code over a single pass through scanhash to
+make sure we're only getting opencl times contributing to the measured
+intervals.
+- Increase curl reaping time to 5 minutes since comms between  curl requests can
+be 2 mins apart with lots of rolltime.
+- No need for extra variable in hash_push.
+- Remove short options -r and -R to allow them to be reused and remove readme
+entries for deprecated options.
+- Deprecate the opt_fail_pause parameter, leaving a null placeholder for
+existing configurations.
+- Free work before retrying in get_work_thread.
+- Don't pause after failed getwork, set lagging flag and reassess.
+- We should not be pausing in trying to resubmit shares.
+- Get rid of the extending fail pause on failed connects since we discard work
+after a period.
+- get_work always returns true so turn it into a void function.
+- get_work never returns false so get rid of fail pause loop.
+- Get rid of pause and retry from get_upstream_work so we only do it from one
+place.
+- Remove all cases where --retries aborts BFGMiner, making it for submission
+retries only, where it makes sense.
+
+
 BFGMiner Version 2.7.0 - August 21, 2012
 
 - Implement a new pool strategy, BALANCE, which monitors work performed per pool

configure.ac

@@ -2,7 +2,7 @@
 ##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
 m4_define([v_maj], [2])
 m4_define([v_min], [7])
-m4_define([v_mic], [0])
+m4_define([v_mic], [1])
 ##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##--##
 m4_define([v_ver], [v_maj.v_min.v_mic])
 m4_define([lt_rev], m4_eval(v_maj + v_min))

debian/changelog

@@ -1,3 +1,16 @@
+bfgminer (2.7.1-0precise1) precise; urgency=low
+
+  * The occasional strange behaviour where lots of work would end up on backup pools in failover mode should be fixed.
+  * The occasional scenario where one pool dies and the others behave like they're slow to provide work should be fixed.
+  * Very high hashrate (U > 100) machines should now be able to work unhindered even on pools that don't support rolltime.
+  * The --retry-pause/-R option no longer does anything and is deprecated in preference for faster communications and simpler code.
+  * -r was removed as a shortcut for --retries.
+  * Hopefully the dynamic mode for GPUs is fixed on windows.
+  * Hopefully the 7 day windows crash bug has been fixed
+
+ -- Luke Dashjr <luke+bfgminer@dashjr.org>  Mon, 21 Aug 2012 16:43:09 -0000
+
+
 bfgminer (2.7.0-0precise1) precise; urgency=low
 
   * The main change in this version is a complete rewrite of the getwork requesting mechanism. Con had been slowly hacking away at the old one for some time, but finally gave up in disgust and has rewritten it to some extent. Previously, mining threads would occasionally throw out a request for more work, some arbitrary test would be done on whether more work should be requested, and it handed off the message to another thread which spawned another thread and that then sent the request and so on. Worse yet it was hard to find the right place to reuse work and so it was never reused to its utmost potential. The rewrite involves scheduling a new request based on the rate the old work items get used up, and is much better at predicting when it needs to leak work to backup pools and less likely to throw a "pool is not providing work fast enough" message. Overall you should now see much more Local Work (LW), the efficiency will be higher on pools that support rolltime, less work will be discarded, any magnitude rig will be kept solidly busy - note this MAY mean your overclocks will become that much more stressed if you have set clocks very aggressively. Thanks to Con and the numerous people who tested this during its development phase.

debian/control

@@ -2,7 +2,7 @@ Source: bfgminer
 Priority: optional
 Section: misc
 Maintainer: Luke Dashjr <luke_bfgminer@dashjr.org>
-Standards-Version: 2.7.0
+Standards-Version: 2.7.1
 Build-Depends: build-essential, debhelper, autoconf, automake, libtool, libssl-dev, yasm, pkg-config, libudev-dev, libcurl4-openssl-dev, wget, unzip, libncurses5-dev, libudev-dev, libusb-1.0-0-dev
 
 Package: bfgminer