twisterarmy/twister-core
1
0
Fork 0
mirror of https://github.com/twisterarmy/twister-core.git synced 2025-01-09 14:28:22 +00:00
Code Issues Projects Releases Wiki Activity
Community driven twister-core
1,875 Commits 3 Branches 17 Tags 21 MiB
C++ 77.1%
HTML 11%
C 4.3%
M4 3.3%
Python 2.4%
Other 1.5%
49e1501b5d
Go to file
Luke Dashjr 49e1501b5d Move QMAKE_LIBS_QT_ENTRY adjustment to bitcoin side of build 
It could just as well be on either part of the gitian build, but to safely put it on the Qt side would require bumping the filename, and every gitian user rebuilding it.
v0.5.3.1 put it on the Bitcoin side, and this is easier to work with and keep safe, so I'm moving it.

Use `qmake MINGW_THREAD_BUGFIX=0` to disable
2012-03-22 12:46:47 -04:00
contrib Move QMAKE_LIBS_QT_ENTRY adjustment to bitcoin side of build 2012-03-22 12:46:47 -04:00
doc add shell one-liner for updating translations in bitcoin.qrc 2012-03-16 19:03:43 +01:00
scripts/qt move qt-specific scripts to qt-specific directory in scripts/ 2011-09-18 12:44:32 +02:00
share Increase client version to 0.6 2012-02-07 11:22:09 -05:00
src Bump CLIENT_VERSION for rc4 release 2012-03-16 15:08:57 -04:00
.gitignore Output build temp files in build/ instead of current directory. 2011-09-26 13:14:34 -04:00
bitcoin-qt.pro Move QMAKE_LIBS_QT_ENTRY adjustment to bitcoin side of build 2012-03-22 12:46:47 -04:00
COPYING Update all copyrights to 2012 2012-02-07 11:28:30 -05:00
INSTALL Update build instructions for the new, no-wxwidgets world 2011-09-26 11:40:43 -04:00
README directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README.md Updated readme file with timers. 2011-09-26 22:22:19 -04:00

README.md

Bitcoin integration/staging tree

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the bitcoin development team members simply pulls it.

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

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 official, stable release versions of Bitcoin. If you would like to help test the Bitcoin core, please contact QA@BitcoinTesting.org.

Feature branches are created when there are major new features being worked on by several people.

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'.

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'.

Requests to reopen closed pull requests and/or issues can be submitted to QA@BitcoinTesting.org.