aboutsummaryrefslogtreecommitdiff
path: root/doc/README_windows.txt
AgeCommit message (Collapse)Author
2017-04-05doc: Remove version numbers from READMEsWladimir J. van der Laan
If we want to keep these numbers, could generate them using autoconf. But this seems unnecessary.
2017-02-17build: bump version to 0.14.99Wladimir J. van der Laan
Now that 0.14 branch has been split off, master is 0.14.99 (pre-0.15). Also clean out release notes.
2016-07-18build: bump version to 0.13.99Wladimir J. van der Laan
Now that 0.13 branch has been split off, master is 0.13.99 (pre-0.14).
2015-12-03Now that 0.12 has been branched, master is 0.12.99Wladimir J. van der Laan
... in preparation for 0.13
2015-06-01Now that 0.11 has been branched, master is 0.11.99Wladimir J. van der Laan
... in preparation for 0.12
2015-01-02Remove redundant copyright notices from README filesWladimir J. van der Laan
The normative place for these for the entire project is COPYING, and the main README already has a MIT license section.
2014-12-19Merge pull request #5470Wladimir J. van der Laan
78253fc Remove references to X11 licence (Michael Ford)
2014-12-17Drop beta suffixes from readmesMichael Ford
2014-12-16Remove references to X11 licenceMichael Ford
2014-12-11Now that 0.10 has been branched, master is 0.10.99Wladimir J. van der Laan
2014-07-29Update openssl.org URL to include https://Jeff Garzik
Suggested by whitj00. Fixes #4595
2014-04-15VERSION obtained from source instead of the previous git tag.Warren Togami
Drawback: The version string is no longer a valid git identifier. For this reason the 'g' short hash prefix has been removed. Exception: When building directly from a tag this behaves exactly like the previous behavior. This allows formatting release versions with precision i.e. v0.9.2 This also allows arbitrary topicbranch names i.e. v0.9.1-glibc-compat
2014-01-29Bump version numbers for 0.9.0rc1 releaseWladimir J. van der Laan
2013-12-13Rebrand to `Bitcoin Core`Wladimir J. van der Laan
Only messages for now, executable names and other file names can be changed later if necessary and safe. Do not do an all-sweeping change. Some occurences of Bitcoin-Qt need to be kept: - Applicationname: this is used to determine the registry entry names, we don't want to lose settings over a silly name change. - Where it refers to the executable name instead of the product name.
2013-05-10Update version numbers for 0.8.2rc1 releasev0.8.2rc1Gavin Andresen
2013-01-30Bump version numbers for 0.8 releaseGavin Andresen
Version numbers changed from 0.7.99 to 0.8.0 Set CLIENT_VERSION_IS_RELEASE to remove pre-release warning Updated copyright in COPYING and doc/READMEs to 2013 Updated doc/release-notes.txt
2012-10-21Update version numbers to 0.7.99Pieter Wuille
2012-10-09Bump versions for 0.7.1 releaseGavin Andresen
2012-08-27Version numbers -> 0.7.0Gavin Andresen
2012-07-18Docs Tidy upfanquake
2012-05-08Increase client version to 0.6.99Gregory Maxwell
2012-05-04Bump version numbers for 0.6.1rc2v0.6.1Gavin Andresen
2012-04-27Bump version numbers for 0.6.1rc1Gavin Andresen
2012-02-07Increase client version to 0.6Gavin Andresen
2011-12-16Bump version 0.5.99 (prep for pulling for version 0.6)Gavin Andresen
2011-11-21Bump version numbers to 0.5.1Gavin Andresen
2011-10-25Update documentation to reflect reality (no win32 gitian builds, new Mac ↵Gavin Andresen
process)
2011-09-26Bump version to 0.4.1Gavin Andresen
2011-09-02Bumped version numbers to 0.4.0rc1v0.4.00rc1Gavin Andresen
2011-07-13Bump version to 0.3.25Jeff Garzik
Yes, we might release as v0.4, but let's just do a simple increment for now.
2011-07-02Bump version to 0.3.24.Jeff Garzik
2011-06-05Bump version to 0.3.23.Jeff Garzik
2011-05-17doc/README: bump version to 0.3.22v0.3.22rc1Jeff Garzik
2011-04-20More 0.3.21 release prepv0.3.21rcGavin Andresen
Bump version number in Windows installer file Update READMEs.
generated by cgit v1.2.3 (git 2.26.2) at 2024-11-01 03:27:03 +0000