From: kmhugo <kmhugo>
Date: Sun, 2 Mar 2003 00:39:23 +0000 (+0000)
Subject: README file for 3.5.0
X-Git-Tag: MOVE2GIT~2128
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=935d283298593f4a77f977645146f7e34eee738b;p=nethack

README file for 3.5.0

The branching process is nearly complete.  The changes below
ought to be applied only to the 3.5.0 trunk.
---

diff --git a/README b/README
index c79ed712a..a67246169 100644
--- a/README
+++ b/README
@@ -1,33 +1,17 @@
-                NetHack 3.4.1 -- General information
+                NetHack 3.5.0 -- General information
 
-NetHack 3.4 is an enhancement to the dungeon exploration game NetHack.
+NetHack 3.5 is an enhancement to the dungeon exploration game NetHack.
 It is a distant descendent of Rogue and Hack, and a direct descendent of
-NetHack 3.3.
-
-NetHack 3.4.1 is a bugfix release for 3.4.0.
- *  Fix a few fatal errors including one for reentering shops, one
-       involving land mines and boulders/statues, one for delayed
-       polymorph, and one for chest traps blowing up a ball and chain
- *  Fix a buffer overflow that could lead to security problems
- *  Hundreds of general bug fixes
- *  Several message and other glitches corrected
- *  Travel command adjustments and ability to disable travel command
- *  message recall window extensions (by Christian Cooper)
- *  win32: some interface improvements
- *  unix: improved tile support
- *  gnome: some fixes, and some enhancements by Dylan Alex Simon
- *  Windows CE port included (by Alex Kompel)
+NetHack 3.4.
+
+NetHack 3.5.0 has many new features.
+ *  List new features here
 
 A fuller list of changes for this release can be found in the file 
-doc/fixes34.1 in the source distribution.  The text in there was written 
+doc/fixes35.0 in the source distribution.  The text in there was written 
 for the development team's own use and is provided "as is", so please do 
 not ask us to further explain the entries in that file.
 
-We've also added a trouble log (paniclog) that will keep a record of the
-details behind a "dungeon collapses" message, or a "perhaps you better
-quit" message to assist in getting the required information included in
-bug reports to us.
-
                         - - - - - - - - - - -
 
 Please read items (1), (2) and (3) BEFORE doing anything with your new code.
@@ -203,13 +187,13 @@ If you've changed something to get NetHack to run on your system, it's likely
 that others have done it by making slightly different modifications.  By routing 
 your patches through the development team, we should be able to avoid making 
 everyone else choose among variant patches claiming to do the same thing, to keep
-most of the copies of 3.4 synchronized by means of official patches, and to 
+most of the copies of 3.5 synchronized by means of official patches, and to 
 maintain the painfully-created file organization.  (This process has been working
 since the time when everyone just posted their own patches to 2.3.  At that time,
 there were no archived bug-fixes to give to people who got 2.3 after its initial
 release, so the same bugs kept being discovered by new batches of people.)
 We have been successful in preventing this from happening since the 3.0
-release.  Please cooperate to keep this from happening to 3.4.
+release.  Please cooperate to keep this from happening to 3.5.
 
 It is inevitable that we will reject some proposed additions of new features
 either because they do not fit our conception of the game, or because they
@@ -218,7 +202,7 @@ you are free, of course, to post the patches to the net yourself and let the
 marketplace decide their worth.
 
 All of this amounts to the following:  If you decide to apply a free-lanced
-patch to your 3.4 code, you are on your own.  In our own patches, we will
+patch to your 3.5 code, you are on your own.  In our own patches, we will
 assume that your code is synchronized with ours.
 
                   -- Good luck, and happy Hacking --