summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorArthur de Jong <arthur@arthurdejong.org>2012-06-17 09:25:03 +0000
committerArthur de Jong <arthur@arthurdejong.org>2012-06-17 09:25:03 +0000
commit1d0006facb1e3db310046ba490c626ed579edb6f (patch)
tree9eed1ad15096453eb2c551f8c77ef784ee7903fe /HACKING
parent978e3fe703192f744e81c9bcf78f88e2004933a0 (diff)
minor documentation touch-ups
git-svn-id: http://arthurdejong.org/svn/nss-pam-ldapd/nss-pam-ldapd@1705 ef36b2f9-881f-0410-afb5-c4e39611909c
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING15
1 files changed, 7 insertions, 8 deletions
diff --git a/HACKING b/HACKING
index a4095d0..a764f3b 100644
--- a/HACKING
+++ b/HACKING
@@ -18,8 +18,8 @@ are considered:
* please follow the existing coding conventions
* please test the patch and include information on testing with the patch
(platforms tested, etc)
-* include a copyright statement in the patched code if you feel the
- contribution is significant enough (e.g. more than a few lines)
+* add a copyright statement with the patch if you feel the contribution is
+ significant enough (e.g. more than a few lines)
* when including third-party code, retain copyright information (copyright
holder and license) and ensure that the license is LGPL compatible
@@ -42,17 +42,16 @@ For building svn snapshots the following tools are needed:
To build the svn snapshot run the autogen.sh shell script to build the
configure script. When developing patches please use --enable-warnings with
-configure and don't introduce too many new warnings. For building the manual
-pages docbook2x is used.
+configure and don't introduce too many new warnings.
RELEASE VERSIONING
==================
-A new versioning scheme was chosen over the nss_ldap release scheme. The
-scheme is a simple major.minor.micro numbering. Until a 1.0 release is made
-the code will be considered work in progress. The interfaces may change and
-features may be added or removed.
+The versioning scheme of nss-pam-ldapd is a simple major.minor.micro
+numbering. The idea is to keep a stable (x.y) branch that only gets bug
+fixes and small enhancements while development goes in another branch.
+Backwards incompatible changes should be announced clearly.
GENERAL DESIGN