Richard Levitte
fcc88e4915
Tagging has been done, move on to develop beta 4 (hopefully not :-)).
2001-03-30 16:22:44 +00:00
Richard Levitte
787f25ab42
Release beta 3 of OpenSSL 0.9.6a.
...
The tag will be OpenSSL_0_9_6a-beta3.
2001-03-30 12:21:28 +00:00
Richard Levitte
b6282a2004
Tagging has been done (OpenSSL_0_9_6a-beta2), time to move on.
2001-03-21 20:54:52 +00:00
Richard Levitte
f14aa30118
Release OpenSSL 0.9.6a beta2.
2001-03-21 20:37:47 +00:00
Richard Levitte
18c497dffb
Tagging has now been done, switch over to development of beta 2.
...
The tag for beta 1 is OpenSSL_0_9_6a-beta1.
2001-03-13 16:29:03 +00:00
Richard Levitte
15922ccdf6
Release Beta 1 of 0.9.6a.
2001-03-13 16:08:32 +00:00
Richard Levitte
eec6e53851
Eh, this branch is not version 0.9.6, it's the development of 0.9.6a.
2001-01-24 16:21:21 +00:00
Richard Levitte
0e8f2fdfdd
Time to build the release. Bump the version info accordingly.
2000-09-24 15:21:30 +00:00
Richard Levitte
d40898dfab
Time to build beta 3. Bump the version numbers accordingly.
2000-09-21 09:08:44 +00:00
Richard Levitte
a440d6636f
A new beta is being released. Change the version numbers
...
accordingly.
2000-09-17 20:19:44 +00:00
Richard Levitte
bed1847b6a
Time to release a beta. Change the version numbers and dates
...
accordingly.
2000-09-11 12:31:36 +00:00
Richard Levitte
b436a98257
Redo and enhance the support for building shared libraries. Currently
...
there's support for building under Linux and True64 (using examples
from the programming manuals), including versioning that is currently
the same as OpenSSL versions but should really be a different series.
With this change, it's up to the users to decide if they want shared
libraries as well as the static ones. This decision now has to be
done at configuration time (well, not really, those who know what they
do can still do it the same way as before).
The OpenSSL programs (openssl and the test programs) are currently
always linked statically, but this may change in the future in a
configurable manner. The necessary makefile variables to enable this
are in place.
Also note that I have done absolutely nothing about the Windows target
to get something similar. On the other hand, DLLs are already the
default there, but without versioning, and I've no idea what the
possibilities for such a thing are there...
2000-07-21 15:08:53 +00:00
Richard Levitte
7c6c052e68
Tagging has now been done, update to the next possible version (I keep
...
a low profile, so we don't get discontinuity in the numbering...)
2000-04-01 11:21:14 +00:00
Richard Levitte
561c71a76b
Building version 0.9.5a
2000-04-01 11:03:41 +00:00
Richard Levitte
90cc4e29b3
Tagging has been done, update to next probable version...
2000-03-23 21:14:11 +00:00
Richard Levitte
0806278561
Time for version 0.9.5a beta2
...
I know it's earlier than announced. The high amount of problems in
beta1 warants this, however.
2000-03-23 21:07:41 +00:00
Richard Levitte
c81ccaddad
Tagging done, we move to the next possible.
2000-03-20 07:47:37 +00:00
Richard Levitte
3cf4f5d05e
Change the version text, it's time to release the first beta of 0.9.5a.
2000-03-20 07:22:47 +00:00
Richard Levitte
e55818b9d3
Change the notation and coding of the version to be able to contain
...
both a patch level and a beta status. IMHO, it also makes more sense
to have beta status be part of the development status than to have it
be an alternate name for patch levels under special conditions.
2000-03-19 09:35:19 +00:00
Richard Levitte
11750113c6
Tagging has been done, time to switch to 0.9.6-dev.
2000-02-28 12:11:39 +00:00
Richard Levitte
74cdf6f73a
Time for a release
2000-02-28 11:59:02 +00:00
Richard Levitte
13bf48c77a
For lack of a better name, this is now called 0.9.5beta3-dev until the
...
release.
2000-02-27 11:12:58 +00:00
Richard Levitte
a1a426ea20
Change version string to reflect the release of beta 2.
2000-02-27 11:07:23 +00:00
Bodo Möller
b05c7211cb
Clarification.
2000-02-25 07:48:02 +00:00
Bodo Möller
f6de86dc3d
Version 0.9.5beta2-dev (so that the next snapshot will not
...
claim to be 0.9.5beta1).
(Are the version number examples correct -- the same numerical
code for:
* 0.9.3beta2-dev 0x00903002
* 0.9.3beta2 0x00903002
?)
2000-02-24 20:40:02 +00:00
Richard Levitte
5921ea3bcf
0.9.5beta1
2000-02-24 02:22:15 +00:00
Ralf S. Engelschall
d91e201e96
Bump after tarball rolling.
...
Friends, feel free to start again hacking for 0.9.5... ;)
1999-08-09 11:14:08 +00:00
Ralf S. Engelschall
2c720c746b
Bump version to 0.9.4
1999-08-09 10:40:38 +00:00
Ben Laurie
80c38957bc
And carry on with development...
1999-05-29 14:18:27 +00:00
Ben Laurie
033d858cc2
Oops!
1999-05-29 14:14:56 +00:00
Ben Laurie
31fab3e8da
Prepare to release 0.9.3a
1999-05-29 14:13:15 +00:00
Ben Laurie
767d6bfb87
Move on to 0.9.4.
1999-05-24 20:59:34 +00:00
Ben Laurie
09befa1905
Here we go: prepare to roll 0.9.3.
1999-05-24 20:52:13 +00:00
Ben Laurie
e09632f986
Move to beta 3.
1999-05-23 16:38:07 +00:00
Ben Laurie
24abc46963
Prepare for final(?) beta.
1999-05-23 16:35:29 +00:00
Ben Laurie
60ed228e71
On seconds thoughts, the version number shoud _never_ decrease.
1999-05-20 19:57:53 +00:00
Ben Laurie
c1c96de01c
Revert.
1999-05-20 19:46:23 +00:00
Ben Laurie
6b6596202b
Prepare for a beta release.
1999-05-20 19:33:46 +00:00
Bodo Möller
06064bb512
Note that the numbering scheme used to be different.
1999-05-19 18:08:35 +00:00
Ben Laurie
e90c772946
Switch to new version numbering scheme.
1999-05-19 17:36:40 +00:00
Ralf S. Engelschall
09ad8001be
Protect applications from failing to compile when they
...
try to directly include opensslv.h.
1999-05-18 09:19:28 +00:00
Ulf Möller
6b01fa6490
pre-0.9.3 development version.
1999-04-01 11:58:28 +00:00
Ben Laurie
b4cadc6e13
Fix security hole.
1999-03-22 12:22:14 +00:00