summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-11-15 00:42:08 +0000
committerChris McDonough <chrism@agendaless.com>2009-11-15 00:42:08 +0000
commit15be26084ee5705b5ae4ed6b6666b43f9d5d7b54 (patch)
treedb331cbc2eb2e2f25c0db221f5b96defca51590a /docs/designdefense.rst
parentf80dc9858fc3d5851a0211f491b653e70e652342 (diff)
downloadpyramid-15be26084ee5705b5ae4ed6b6666b43f9d5d7b54.tar.gz
pyramid-15be26084ee5705b5ae4ed6b6666b43f9d5d7b54.tar.bz2
pyramid-15be26084ee5705b5ae4ed6b6666b43f9d5d7b54.zip
They can ignore it.
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 5ef52245f..c73636f23 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -946,6 +946,16 @@ for this: the developer of an application that defines custom
plugpoints for its deployers will need to understand the ZCA or he
will need to develop his own similar extensibility system.
+Ultimately, any argument about whether the extensibility features lent
+to applications by :mod:`repoze.bfg` are "good" or "bad" is somewhat
+pointless. You needn't take advantage of the extensibility features
+provided by a particular :mod:`repoze.bfg` application in order to
+affect a modification for a particular set of its deployments. You
+can ignore the application's extensibility plugpoints entirely, and
+instead use version control branching and merging to manage
+application deployment modifications instead, as if you were deploying
+an application written using any other web framework.
+
Other Challenges
----------------