Tidies for 8.02-RC1 release.

git-svn-id: svn://vcs.exim.org/pcre/code/trunk@507 2f5784b3-3f2a-0410-8824-cb99058d5e15

1 files changed, 20 insertions, 12 deletions

diff --git a/maint/README b/maint/README
index aab8009..82062ea 100644
--- a/maint/README
+++ b/maint/README
@@ -1,5 +1,5 @@
 MAINTENANCE README FOR PCRE
----------------------------
+===========================
 
 The files in the "maint" directory of the PCRE source contain data, scripts,
 and programs that are used for the maintenance of PCRE, but which do not form
@@ -14,14 +14,14 @@ also contains some notes for maintainers. Its contents are:
 
 
 Files in the maint directory
-----------------------------
+============================
 
------------------ This file is now OBSOLETE and no longer used ----------------
+---------------- This file is now OBSOLETE and no longer used ----------------
 Builducptable    A Perl script that creates the contents of the ucptable.h file
                  from two Unicode data files, which themselves are downloaded
                  from the Unicode web site. Run this script in the "maint"
                  directory.
------------------ This file is now OBSOLETE and no longer used ----------------
+---------------- This file is now OBSOLETE and no longer used ----------------
 
 GenerateUtt.py   A Python script to generate part of the pcre_tables.c file
                  that contains Unicode script names in a long string with
@@ -61,7 +61,7 @@ utf8.c           A short, freestanding C program for converting a Unicode code
 
 
 Updating to a new Unicode release
----------------------------------
+=================================
 
 When there is a new release of Unicode, the files in Unicode.tables must be
 refreshed from the web site. If the new version of Unicode adds new character
@@ -88,7 +88,7 @@ of Unicode script names.
 
 
 Preparing for a PCRE release
-----------------------------
+============================
 
 This section contains a checklist of things that I consult before building a
 distribution for a new release.
@@ -135,7 +135,9 @@ distribution for a new release.
   Many of these won't need changing, but over the long term things do change.
 
 . Man pages: Check all man pages for \ not followed by e or f or " because
-  that indicates a markup error.
+  that indicates a markup error. However, there is one exception: pcredemo.3, 
+  which is created from the pcredemo.c program. It contains three instances
+  of \\n. 
 
 . When the release is built, test it on a number of different operating
   systems if possible, and using different compilers as well. For example,
@@ -145,7 +147,7 @@ distribution for a new release.
 
 
 Making a PCRE release
----------------------
+=====================
 
 Run PrepareRelease and commit the files that it changes (by removing trailing
 spaces). Then run "make distcheck" to create the tarballs and the zipball.
@@ -155,11 +157,12 @@ Double-check with "svn status", then create an SVN tagged copy:
            svn://vcs.exim.org/pcre/code/tags/pcre-8.xx 
 
 Don't forget to update Freshmeat when the new release is out, and to tell
-webmaster@pcre.org and the mailing list.
+webmaster@pcre.org and the mailing list. Also, update the list of version 
+numbers in Bugzilla (edit products).
 
 
 Future ideas (wish list)
-------------------------
+========================
 
 This section records a list of ideas so that they do not get forgotten. They
 vary enormously in their usefulness and potential for implementation. Some are
@@ -280,7 +283,7 @@ others are relatively new.
 . Callouts with arguments: (?Cn:ARG) for instance.
 
 . A user is going to supply a patch to generalize the API for user-specific 
-  memory allocation so that it is more flexible in threaded environments. Thiw 
+  memory allocation so that it is more flexible in threaded environments. This
   was promised a long time ago, and never appeared...
   
 . Write a function that generates random matching strings for a compiled regex.
@@ -309,8 +312,13 @@ others are relatively new.
 . PCRE cannot at present distinguish between subpatterns with different names,
   but the same number (created by the use of ?|). In order to do so, a way of 
   remembering *which* subpattern numbered n matched is needed. Bugzilla #760.
+  
+. Instead of having #ifdef HAVE_CONFIG_H in each module, put #include 
+  "something" and the the #ifdef appears only in one place, in "something".
+  
+. Support for (*MARK) and arguments for (*PRUNE) and friends. 
 
 Philip Hazel
 Email local part: ph10
 Email domain: cam.ac.uk
-Last updated: 26 September 2009
+Last updated: 10 March 2010