b67eb8dde8
doc: Remove version numbers from READMEs
...
If we want to keep these numbers, could generate them using autoconf.
But this seems unnecessary.
8 years ago
f87e8f5392
build: bump version to 0.14.99
...
Now that 0.14 branch has been split off, master is 0.14.99 (pre-0.15).
Also clean out release notes.
8 years ago
6c0336c772
build: bump version to 0.13.99
...
Now that 0.13 branch has been split off, master is 0.13.99 (pre-0.14).
8 years ago
c12ff995f7
Now that 0.12 has been branched, master is 0.12.99
...
... in preparation for 0.13
9 years ago
3e8ccc765a
Now that 0.11 has been branched, master is 0.11.99
...
... in preparation for 0.12
10 years ago
e6df2bb48f
Remove redundant copyright notices from README files
...
The normative place for these for the entire project is COPYING,
and the main README already has a MIT license section.
10 years ago
e85855fa55
Drop beta suffixes from readmes
10 years ago
78253fcbad
Remove references to X11 licence
10 years ago
d7492304e9
Now that 0.10 has been branched, master is 0.10.99
10 years ago
6b5ee2e092
Update openssl.org URL to include https://
...
Suggested by whitj00. Fixes #4595
10 years ago
3d20cd5f61
VERSION obtained from source instead of the previous git tag.
...
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
11 years ago
f9a2f08882
Bump version numbers for 0.9.0rc1 release
11 years ago
22f0135df0
Rebrand to `Bitcoin Core`
...
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.
11 years ago
5b5d399593
Update version numbers for 0.8.2rc1 release
12 years ago
d38c6488d0
Bump version numbers for 0.8 release
...
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
12 years ago
fcfa7a588e
Update version numbers to 0.7.99
12 years ago
1d1f32d16d
Bump versions for 0.7.1 release
12 years ago
03fa53a640
Version numbers -> 0.7.0
12 years ago
f00a0dcfed
Docs Tidy up
12 years ago
a5f95d75a1
Increase client version to 0.6.99
13 years ago
397737b913
Bump version numbers for 0.6.1rc2
13 years ago
2c31cfc271
Bump version numbers for 0.6.1rc1
13 years ago
6bf4253a68
Increase client version to 0.6
13 years ago
8896c2d9d6
Bump version 0.5.99 (prep for pulling for version 0.6)
13 years ago
795faa595c
Bump version numbers to 0.5.1
13 years ago
7ec064b88e
Update documentation to reflect reality (no win32 gitian builds, new Mac process)
13 years ago
6b8a5ab622
Bump version to 0.4.1
13 years ago
7464e647de
Bumped version numbers to 0.4.0rc1
13 years ago
24a0def8cd
Bump version to 0.3.25
...
Yes, we might release as v0.4, but let's just do a simple increment
for now.
14 years ago
b4b536d782
Bump version to 0.3.24.
14 years ago
6f07e22210
Bump version to 0.3.23.
14 years ago
270e944e30
doc/README: bump version to 0.3.22
14 years ago
ca5884873e
More 0.3.21 release prep
...
Bump version number in Windows installer file
Update READMEs.
14 years ago
Wladimir J. van der Laan