]> jfr.im git - irc/evilnet/x3.git/blame - NEWS
Checking in some .in files for compiling without autoconf/automake trouble
[irc/evilnet/x3.git] / NEWS
CommitLineData
d76ed9a9
AS
1News for srvx release 0.9.5
2[March 21, 2001 - Present]
3---------------------------
4- 0.9.5 released March 21, 2001.
5- This is the LAST release before 1.0 goes out.
6- We came across a (large) memory leak in FreeBSD's libc and worked
7 around it. We also submitted a bug report to the FreeBSD team.
8- As far as we know, no more serious bugs are present in srvx. Most
9 development before 1.0 will be tweaking and minor fixups.
10- Helpfiles should be up to date before the release of 1.0.
11- Just showing off srvx's speed:
12 <@Jedi> ?timecmd trace count host *
13 -OpServX(OpServX@Services.GamesNET.net)- Found 4593 matches.
14 -OpServX(OpServX@Services.GamesNET.net)- Command `trace' finished in 0.003037 seconds.
15
16
17News for everything prior to 0.9.5
18[April 16, 2000 - March 20, 2001]
19----------------------------------
20- Coding began about 1 year prior to the 0.9.5 release.
21- Documentation up to 0.9.5 is virtually non-existant.
22- PRE01 released April 16, 2000.
23- PRE02 released April 18, 2000.
24- After the main parts were completed, it all came down to bug fixing.
25- 0.1 released June 13, 2000.
26- srvx was setup on a machine and linked to GamesNET for its initial beta
27 tests. Many many many bugs were fixed in the first week, fewer as time
28 went along.
29- 0.2 released July 5, 2000.
30- Between 0.2 and 0.7 code for the services themselves was put in. Prior
31 to this was mainly core coding.
32- Using dmalloc, bounds-checking and new log replaying code, we were able
33 to hammer out alot bugs, some of which were severe enough to cause a
34 segfault.
35- 0.7 released December 15, 2000. [0.3 through 0.6 never released]
36- 0.9 released January 17, 2001. [0.8 never released]
37- Just prior to the 0.9.5 release, numerous memory leaks were fixed,
38 prompting the release of 0.9.5.
39- srvx is still running smoothly on GamesNET. If we didn't take it down
40 every 2 days to be updated with new patches, its uptime would be quite
41 high.