Version bump for Beta 2.3
Merge pull request #887 from dionyziz/beta_2_3_changelog

Version bump for Beta 2.3.
Version bump to 0.3.0.
Changelog for Beta 3.0
Quick fix test for sqlite different thread issue.

Found this solution on a stackoverflow thread.
I'm not sure if it fixes the problem as I can't replicate it
myself.

If you are getting this issue, please test this pull request

git remote add gubatron https://github.com/gubatron/OpenBazaar
git fetch gubatron
git checkout experimental-fix-sqlite-different-thread-issue-654

run openbazaar and let me know if the issue persists, or if now
this is causing even weirder issues.

This is far from the ideal solution, but it might fix the problem.

The right solution might be (if we need db fetched objects on another
thread) having a DB-querying thread which is responsible for performing
all DB fetch operations and keeping the consumable outputs
in a temporary container (dict or queue) which is then consumed by
other threads.
Disable sqlite same thread check. (Re:Issue #654)
Merge pull request #921 from gubatron/release-0.3.0

Disable sqlite same thread check. (Re:Issue #654)
Overwrite pystun server list.

* Non-responding servers in pystun's builtin list are causing node to
  crash upon starting up.
network_utils.stun_servers_status_report(server_list)

Given a list of stun servers, probes them and prints out
a report. Useful whenever we want to update the list of
STUN servers to use.
updated STUN server list.
Merge pull request #2 from gubatron/fix_STUN_check

network_utils.stun_servers_status_report(server_list)
Various build and style fixes.

* Rename list to _STUN_SERVERS.
* Remove stun.iptel.org
* Abstract get_NAT_status to work with a specific hostname.
* Remove summary report to enable better automation.
* Add a main function to call test_stun_servers.
Merge pull request #922 from Renelvon/fix_STUN_check

Overwrite pystun server list.
use thread locking to serialize all db access

also reenable check_same_thread so we get exceptions instead of crashes,
although that shouldn't be possible anymore with this locking in place

Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
Merge pull request #937 from benemorius/db-locking

use thread locking to serialize all db access
Revert "Disable sqlite same thread check. (Re:Issue #654)"

This reverts commit 03780eab62d3aabce9036e947bfa5faa77ece451.

* Disabled thread checks may cause sqlite3 to fail in unexpected,
  difficult-to-trace ways. The threading issue shall be resolved more
  systematically in the future.
Merge pull request #940 from Renelvon/enable_thread_checks

Re-enable DB threading checks
Use booleans properly.
Use new octal notation (PEP 3127).
Added test for dbstore.getOrCreate

Fixed syntax