@fuzzy !!WOW!! What effort you are putting forth here. Host, bookkeeper, key grip, the list goes on. Thanks so much.

Please mark me down as "fox" for all columns, as my mobile is failing to comment on the document at this time (surely it cannot be _my_ issue).

Using the CLI you may get your version number within the client by issuing:
get_info
You may also get the version number from the command line by starting the client with the version switch:
./bitshare_client --version

Requesting assistance with building Graphene on Ubuntu 14.04LTS.  I have reviewed the Build Ubuntu documentation for Graphene [1] and taken care to verify Boost 1.57 is referenced within the CMake script.  However, the build fails within 'project_secp256k1' with the output:
[  6%] Performing autogen step for 'project_secp256k1'
/home/myUser/graphene/libraries/fc/vendor/secp256k1-zkp/autogen.sh: 3: /home/myUser/graphene/libraries/fc/vendor/secp256k1-zkp/autogen.sh: autoreconf: not found
make[2]: *** [libraries/fc/vendor/secp256k1-zkp/src/project_secp256k1-stamp/./project_secp256k1-autogen] Error 127
make[1]: *** [libraries/fc/CMakeFiles/project_secp256k1.dir/all] Error 2
make: *** [all] Error 2
myHost:~/graphene$
[1] https://github.com/cryptonomex/graphene/wiki/build-ubuntu

I did review closed Issue #76 [2] which references this library and similar build issues.  Those changes were merged into Master three weeks back, so perhaps this is new, yet related.
[2] https://github.com/cryptonomex/graphene/issues/76

For troubleshooting purposes I'll include:

• My Graphene Build Script
• CMake Output
• Make Output

My Graphene Build Script
# Prep Server
sudo apt-get update
sudo apt-get -y install dphys-swapfile

# Install Prerequisite Packages
sudo apt-get -y install ntp cmake git libreadline-dev uuid-dev g++ libdb++-dev libdb-dev zip libssl-dev openssl build-essential python-dev autotools-dev libicu-dev libbz2-dev libboost-dev libboost-all-dev

# Install Boost 1.57
wget -c 'http://sourceforge.net/projects/boost/files/boost/1.57.0/boost_1_57_0.tar.bz2/download'
tar -xf download
cd boost_1_57_0/
./bootstrap.sh --prefix=/usr/local/
./b2 install

# Install Graphene
git clone https://github.com/cryptonomex/graphene.git
git submodule update --init --recursive
cmake -DBOOST_ROOT="/usr/local/" -DCMAKE_BUILD_TYPE=Debug .
make -j4

CMake Output
myHost:~/graphene$ sudo cmake -DBOOST_ROOT="/usr/local/" -DCMAKE_BUILD_TYPE=Debug .
-- Using custom FindBoost.cmake
-- Boost version: 1.57.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   system
--   filesystem
--   program_options
--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
-- Using custom FindBoost.cmake
-- Boost version: 1.57.0
-- Found the following Boost libraries:
--   coroutine
-- Configuring Graphene on Linux
-- Using  as BerkeleyDB root
-- Looking for: db_cxx-6.0
-- debug/usr/lib/x86_64-linux-gnu/libdb_cxx.sooptimized/usr/lib/x86_64-linux-gnu/libdb_cxx.so
-- Configuring project fc located in: /home/myUser/graphene/libraries/fc
-- Configuring fc to build on Unix/Apple
-- Using custom FindBoost.cmake
-- Boost version: 1.57.0
-- Found the following Boost libraries:
--   thread
--   date_time
--   system
--   filesystem
--   program_options
--   signals
--   serialization
--   chrono
--   unit_test_framework
--   context
--   locale
--   iostreams
--   coroutine
** websocketpp

=========== Used Build Configuration =============

-- ENABLE_CPP11        = ON
-- BUILD_EXAMPLES      = OFF
-- BUILD_TESTS         = OFF

-- WEBSOCKETPP_ROOT    = /home/myUser/graphene/libraries/fc/vendor/websocketpp
-- WEBSOCKETPP_BIN     = /home/myUser/graphene/libraries/fc/vendor/websocketpp/bin
-- WEBSOCKETPP_LIB     = /home/myUser/graphene/libraries/fc/vendor/websocketpp/lib
-- Install prefix      = /usr/local

-- WEBSOCKETPP_BOOST_LIBS        =
-- WEBSOCKETPP_PLATFORM_LIBS     =
-- WEBSOCKETPP_PLATFORM_TSL_LIBS =

-- Could NOT find Curses (missing:  CURSES_LIBRARY CURSES_INCLUDE_PATH)
-- Finished fc module configuration...
-- Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE)
-- Configuring done
-- Generating done
-- Build files have been written to: /home/myUser/graphene

Make Output
myHost:~/graphene$ sudo make
[  0%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/api.cpp.o
[  1%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/buffer.cpp.o
[  1%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/cache.cpp.o
[  2%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/ccc.cpp.o
[  2%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/channel.cpp.o
[  3%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/common.cpp.o
[  3%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/core.cpp.o
[  4%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/epoll.cpp.o
[  4%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/list.cpp.o
[  5%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/md5.cpp.o
[  5%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/packet.cpp.o
[  6%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/queue.cpp.o
[  6%] Building CXX object libraries/fc/vendor/udt4/CMakeFiles/udt.dir/src/window.cpp.o
Linking CXX static library libudt_debug.a
[  6%] Built target udt
[  6%] Performing autogen step for 'project_secp256k1'
/home/myUser/graphene/libraries/fc/vendor/secp256k1-zkp/autogen.sh: 3: /home/myUser/graphene/libraries/fc/vendor/secp256k1-zkp/autogen.sh: autoreconf: not found
make[2]: *** [libraries/fc/vendor/secp256k1-zkp/src/project_secp256k1-stamp/./project_secp256k1-autogen] Error 127
make[1]: *** [libraries/fc/CMakeFiles/project_secp256k1.dir/all] Error 2
make: *** [all] Error 2
myHost:~/graphene$

Any suggestion for troubleshooting is greatly appreciated.

Welcome NickJames to the boards. As you continue to explore BitShares and the community members, add those delegates to you slate that you feel deserve your support. Many have their delegate names in their signature, as they mm not match their forum name.

Personal recommendation for your consideration:
1.  Choose delegates that produce blocks properly (remove those that don't; the point of this thread)
2.  Choose a diverse set of delegates rather than multiple from a single entity (support decentralization)
3.  Choose delegates that publish accurate feeds (remind those not doing so)
4.  Send a transaction to yourself with your BTS stake to complete the vote (repeat after each update)

Again, welcome,
Fox

Yes, both Graphene and BitShares currently run on the RPi2. You must comment out the Salsa references in the build scripts to compile correctly, as they will not build on the RPi2 processor at this time.

Great work by the entire Beyond Bitcoins Team. Well deserved. Really appreciate your efforts and community building.

I have some concerns about the bts/0.9.2 release as I do not see the code previously released to the dvs/0.9.x network for testing.  It is my understanding that all code in BitShares will go through DevShares first for testing.

DevShares:
20 APR 2015 | Latest commit [1]

BitShares:
18 MAY 2015 | bts/0.9.2 [2]
04 MAY 2015 | bts/0.9.1
24 APR 2015 | bts/0.9.0

Request:
Please help me understand the decision process used to release the bts/0.9.2 code into the BitShares network. 

References:
[1] https://github.com/BitShares/DevShares/commits/master
[2] https://github.com/BitShares/bitshares/commits/master

Quote from: bitscape on May 07, 2015, 08:05:01 pm

Quote from: bytemaster on May 07, 2015, 12:18:59 pm

In the event that Invictus is fined it will not impact the future of BitShares, it will only impact my own personal financial situation.   I suspect that this community would have my back and we will all move past it.

There is nothing to fear except fear itself.

Yup, there I am.

No, in the back behind the scenes. That's me. Not a Super Hero; just keeping the network running for this community. Now get out the vote won't ya! 
-Fox