com php-src: Mention git and suggest PECL for new things: CODING_STANDARDS
| From: | Johannes Schlüter | Date: | Fri, 19 Jul 2013 20:05:52 +0000 |
| Subject: | com php-src: Mention git and suggest PECL for new things: CODING_STANDARDS | ||
| Groups: | php.cvs | ||
| Request: | Send a blank email to php-cvs+get-72701@lists.php.net to get a copy of this message | ||
Commit: 7daf1a6c1473e4d5f414256c02944527f2ec3c63
Author: Johannes Schlüter <johannes@php.net> Fri, 19 Jul 2013 22:05:52 +0200
Parents: b278aba429ee86574f3f02294ffbcd4e858b15b1
Branches: master
Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=7daf1a6c1473e4d5f414256c02944527f2ec3c63
Log:
Mention git and suggest PECL for new things
Changed paths:
M CODING_STANDARDS
Diff:
diff --git a/CODING_STANDARDS b/CODING_STANDARDS
index 7413be4..16ec36b 100644
--- a/CODING_STANDARDS
+++ b/CODING_STANDARDS
@@ -259,7 +259,10 @@ The file labelled 'EXPERIMENTAL' should include the following
information::
Any authoring information (known bugs, future directions of the module).
- Ongoing status notes which may not be appropriate for SVN comments.
+ Ongoing status notes which may not be appropriate for Git comments.
+
+In general new features should go to PECL or experimental branches until
+there are specific reasons for directly adding it to the core distribution.
Aliases & Legacy Documentation
-----------------------------------