Update README to outline tagging policy and include relevant info links

README.md

@@ -2,32 +2,28 @@ POD-CryptoAsian
 
 XCash development tree
 
-XCash is a PoS-based cryptocurrency.
+XCash is a PoS-based cryptocurrency that was the 1st to feature stealth
+addresses used from the genesis block during the mining period, with
+stealth addresses the default.
+
+Bitcointalk Thread:  https://bitcointalk.org/index.php?topic=765360.640
+IRC Channel:  #xcash on irc.freenode.net
+Twitter: https://twitter.com/XCashcoin
 
 Development process
 ===========================
 
-Developers work in their own trees, then submit pull requests when
-they think their feature or bug fix is ready.
-
-The patch will be accepted if there is broad consensus that it is a
-good thing.  Developers should expect to rework and resubmit patches
-if they don't match the project's coding conventions (see coding.txt)
-or are controversial.
-
 The master branch is regularly built and tested, but is not guaranteed
 to be completely stable. Tags are regularly created to indicate new
 stable release versions of XCash.
 
-Feature branches are created when there are major new features being
-worked on by several people.
+The master branch is likely to be unstable or contain work-in-progress
+as new features are built and readied for the next release.
 
-From time to time a pull request will become outdated. If this occurs, and
-the pull is no longer automatically mergeable; a comment on the pull will
-be used to issue a warning of closure. The pull will be closed 15 days
-after the warning if action is not taken by the author. Pull requests closed
-in this manner will have their corresponding issue labeled 'stagnant'.
+XCash aims for a regular release cycle of features following a bi-weekly
+pace, although the timeframe may vary depending on the complexity of
+the backlog.  XCash is building a large array of wallet features and 
+network/daemon infrastructure to support a large and dynamic ecosystem.
 
-Issues with no commits will be given a similar warning, and closed after
-15 days from their last activity. Issues closed in this manner will be 
-labeled 'stale'.
+Service providers and users should always use the latest tagged release
+version.