summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStuart Rackham <srackham@methods.co.nz>2011-02-19 12:55:53 +1300
committerStuart Rackham <srackham@methods.co.nz>2011-02-19 12:55:53 +1300
commitefc63e277c3375dce1fc6459edb584569584c4a3 (patch)
treedf47007d62cd6158f2d0494649bb5c46e2dd8f72
parent8e5032c1692cd01d4f90c42c5f8f0caf59299339 (diff)
downloadasciidoc-efc63e277c3375dce1fc6459edb584569584c4a3.tar.gz
- Bumped version number.
- Documentation updates.
-rwxr-xr-xa2x.py2
-rwxr-xr-xasciidoc.py2
-rw-r--r--common.aap2
-rw-r--r--configure.ac2
-rw-r--r--examples/website/filters.txt2
-rw-r--r--examples/website/index.txt39
6 files changed, 44 insertions, 5 deletions
diff --git a/a2x.py b/a2x.py
index e477d52..3582a96 100755
--- a/a2x.py
+++ b/a2x.py
@@ -21,7 +21,7 @@ import urlparse
import zipfile
PROG = os.path.basename(os.path.splitext(__file__)[0])
-VERSION = '8.6.4_beta_1'
+VERSION = '8.6.4'
# AsciiDoc global configuration file directory.
# NOTE: CONF_DIR is "fixed up" by Makefile -- don't rename or change syntax.
diff --git a/asciidoc.py b/asciidoc.py
index 77183c0..44eb624 100755
--- a/asciidoc.py
+++ b/asciidoc.py
@@ -9,7 +9,7 @@ under the terms of the GNU General Public License (GPL).
import sys, os, re, time, traceback, tempfile, subprocess, codecs, locale, unicodedata
### Used by asciidocapi.py ###
-VERSION = '8.6.4_beta_1' # See CHANGLOG file for version history.
+VERSION = '8.6.4' # See CHANGLOG file for version history.
MIN_PYTHON_VERSION = 2.4 # Require this version of Python or better.
diff --git a/common.aap b/common.aap
index 8d91ac9..73cf83a 100644
--- a/common.aap
+++ b/common.aap
@@ -2,7 +2,7 @@
# Executed by all main.aap's before anything else.
#
-_parent.VERS = 8.6.4_beta_1
+_parent.VERS = 8.6.4
_parent.DATE = 17 February 2011
all:
diff --git a/configure.ac b/configure.ac
index 93be64f..0665b79 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,4 +1,4 @@
-AC_INIT(asciidoc, 8.6.4_beta_1)
+AC_INIT(asciidoc, 8.6.4)
AC_CONFIG_FILES(Makefile)
diff --git a/examples/website/filters.txt b/examples/website/filters.txt
index cc0382a..24dd81c 100644
--- a/examples/website/filters.txt
+++ b/examples/website/filters.txt
@@ -3,7 +3,7 @@ AsciiDoc Filters
AsciiDoc link:userguide#X59[filters] allow external commands to
-process AsciiDoc 'Paragraphs', 'DelimitedBlocks' and 'Table' content.
+process AsciiDoc 'Paragraph', 'DelimitedBlock' and 'Table' contents.
Filters are primarily an extension mechanism for generating
specialized outputs. Filters are available as external
<<_filter_plugins,plugins>> and come
diff --git a/examples/website/index.txt b/examples/website/index.txt
index da13ae3..3483688 100644
--- a/examples/website/index.txt
+++ b/examples/website/index.txt
@@ -399,3 +399,42 @@ link:latex-bugs.html[Geoff's notes]).
It's probably also worth pointing out that LaTeX output can be
generated by passing AsciiDoc generated DocBook through `dblatex(1)`.
+
+
+Patches and bug reports
+-----------------------
+Patches and bug reports are are encouraged, but please try to follow
+these guidelines:
+
+- Post bug reports and patches to the
+ http://groups.google.com/group/asciidoc[asciidoc discussion list],
+ this keeps things transparent and gives everyone a chance to
+ comment.
+- The email subject line should be a specific and concise topic
+ summary. Commonly accepted subject line prefixes such as '[ANN]',
+ '[PATCH]' and '[SOLVED]' are good.
+
+=== Bug reports
+- When reporting problems please illustrate the problem with the
+ smallest possible example that replicates the issue (and please test
+ your example before posting). This technique will also help to
+ eliminate red herrings before you post the problem.
+- Paste the commands that you executed along with any relevant
+ outputs.
+- Include the version of AsciiDoc and the platform you're running it
+ on.
+- If you can program please consider writing a patch to fix the
+ problem.
+
+=== Patches
+- Keep patches small and atomic (one issue per patch) -- no patch
+ bombs.
+- If possible test your patch against the current trunk.
+- If your patch adds or modifies functionality include a short example
+ that illustrates the changes.
+- Send patches in `diff -u` format, inline inside the mail message is
+ usually best; if it is a very long patch then send it as an
+ attachment.
+- Include documentation updates if you're up to it; otherwise insert
+ 'TODO' comments at relevant places in the documentation.
+