Updated README.md to reflect changes to QA process #488

pull alexwaters wants to merge 0 commits into bitcoin:master from alexwaters:master changing 0 files +0 −0

alexwaters commented at 11:46 PM on September 2, 2011: contributor

No description provided.
jgarzik commented at 3:20 AM on September 3, 2011: contributor

ACK
alexwaters commented at 5:03 AM on September 3, 2011: contributor

Would anyone be opposed to adding a timer on issues, for instance:

"Non-bug issues will be removed if no commits or comments are made in 30 days since issue creation."
TheBlueMatt commented at 6:20 AM on September 3, 2011: member

Who holds the keys to BitcoinQA@gmail.com?
alexwaters commented at 6:22 AM on September 3, 2011: contributor

I do - maybe it should be passed to Gavin? Currently it's forwarding to my email address.
TheBlueMatt commented at 6:30 AM on September 3, 2011: member

IMHO more than one person should hold the keys. As long as multiple people can get to the account.

in README.md:None in c134c3f955 outdated

  11 | +If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list:  http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development
  12 |  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.
  13 |  
  14 | -The master branch is regularly built and tested (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.
  15 | -
  16 | +The master branch is regularly built and tested, and periodically pushed to the git repo to become the official, stable, released bitcoin. If you would like to help test the Bitcoin core, please contact BitcoinQA@Gmail.com

TheBlueMatt commented at 6:35 AM on September 3, 2011:

The git repo is the master branch, or is that changing?

in README.md:None in e860eb8b24 outdated

  11 | +If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list:  http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development
  12 |  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.
  13 |  
  14 | -The master branch is regularly built and tested (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.
  15 | -
  16 | +The binaries are regularly built and tested, and periodically pushed to the Git repo to become the official, stable, released bitcoin. If you would like to help test the Bitcoin core, please contact BitcoinQA@Gmail.com

TheBlueMatt commented at 7:54 PM on September 5, 2011:

I'd suggest The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Bitcoin. If you would like to help test the Bitcoin core, please contact BitcoinQA@Gmail.com. I also like sipa's suggestion of an email that is @bitcoin.org

alexwaters commented at 1:26 AM on September 6, 2011: contributor

totally F'd up with that last commit - still learning git, sorry!
alexwaters merged this on Sep 6, 2011
alexwaters closed this on Sep 6, 2011
ptschip referenced this in commit 54d1009b23 on May 2, 2017
lateminer referenced this in commit adf9c811e4 on Jul 17, 2020
rajarshimaitra referenced this in commit 44717c26cf on Aug 5, 2021
DrahtBot locked this on Sep 8, 2021

Contributors

Labels

Linked (view graph)

#495 Updated readme file