cvs: peclweb /public_html index.php support.php /public_html/doc branches.php index.php

From: Date: Fri, 10 Sep 2004 09:18:13 +0000
Subject: cvs: peclweb /public_html index.php support.php /public_html/doc branches.php index.php
Groups: php.pecl.cvs 
Request: Send a blank email to pecl-cvs+get-1809@lists.php.net to get a copy of this message
wez Fri Sep 10 05:18:13 2004 EDT Added files: /peclweb/public_html/doc branches.php Modified files: /peclweb/public_html index.php support.php /peclweb/public_html/doc index.php Log: add some docs on branching in our CVS http://cvs.php.net/diff.php/peclweb/public_html/index.php?r1=1.77&r2=1.78&ty=u Index: peclweb/public_html/index.php diff -u peclweb/public_html/index.php:1.77 peclweb/public_html/index.php:1.78 --- peclweb/public_html/index.php:1.77 Sun Sep 21 08:03:34 2003 +++ peclweb/public_html/index.php Fri Sep 10 05:18:10 2004 @@ -15,7 +15,7 @@ +----------------------------------------------------------------------+ | Authors: Martin Jansen <mj@php.net> | +----------------------------------------------------------------------+ - $Id: index.php,v 1.77 2003/09/21 12:03:34 mj Exp $ + $Id: index.php,v 1.78 2004/09/10 09:18:10 wez Exp $ */ $SIDEBAR_DATA=' @@ -40,6 +40,7 @@ //echo menu_link("About PEAR", "/manual/en/about-pear.php"); //echo menu_link("Manual", "/manual/"); //echo menu_link("Frequently Asked Questions", "/manual/en/faq.php"); +echo menu_link("PECL specific docs", "/doc/index.php"); echo menu_link("Mailing Lists & Support Resources", "/support.php"); echo '</div>'; echo '<h2>Downloads</h2>'; http://cvs.php.net/diff.php/peclweb/public_html/support.php?r1=1.65&r2=1.66&ty=u Index: peclweb/public_html/support.php diff -u peclweb/public_html/support.php:1.65 peclweb/public_html/support.php:1.66 --- peclweb/public_html/support.php:1.65 Mon Feb 2 13:12:06 2004 +++ peclweb/public_html/support.php Fri Sep 10 05:18:10 2004 @@ -15,7 +15,7 @@ +----------------------------------------------------------------------+ | Authors: | +----------------------------------------------------------------------+ - $Id: support.php,v 1.65 2004/02/02 18:12:06 jon Exp $ + $Id: support.php,v 1.66 2004/09/10 09:18:10 wez Exp $ */ $SIDEBAR_DATA=''; @@ -181,6 +181,7 @@ by Derick Rethans</li> <li><a href="http://talks.php.net/show/extending-php-apachecon2003">Writing a PHP Extension (PHP 4), Apachecon November 19, 2003. Las Vegas, NV</a> by Jim Winstead</li> + <li><a href="http://www.php.net/~wez/extending-php.pdf">Extending PHP: a 3 hour tutorial, PHP{Con West, Santa Clara, October 2003 (PDF)</a> by Wez Furlong</li> <li><a href="http://www.derickrethans.nl/ze-ext/talk.html">Zend and Extending PHP (PHP 4), PHP Forum 2002 Paris, France - December 10, 2002</a> by Derick Rethans</li> </ul> http://cvs.php.net/diff.php/peclweb/public_html/doc/index.php?r1=1.6&r2=1.7&ty=u Index: peclweb/public_html/doc/index.php diff -u peclweb/public_html/doc/index.php:1.6 peclweb/public_html/doc/index.php:1.7 --- peclweb/public_html/doc/index.php:1.6 Fri Feb 8 09:40:38 2002 +++ peclweb/public_html/doc/index.php Fri Sep 10 05:18:13 2004 @@ -1 +1,13 @@ -<?php Header("Location: http://pear.php.net/manual/en/"); ?> +<?php # $Id: index.php,v 1.7 2004/09/10 09:18:13 wez Exp $ +response_header("PECL specific docs"); +?> + +<h2>Some information on PECL specific topics</h2> + +<ul> +<li><a href="branches.php">CVS Branches and how they relate to PECL</a></li> +</ul> + +<?php +response_footer(); +?> http://cvs.php.net/co.php/peclweb/public_html/doc/branches.php?r=1.1&p=1 Index: peclweb/public_html/doc/branches.php +++ peclweb/public_html/doc/branches.php <?php # $Id: branches.php,v 1.1 2004/09/10 09:18:13 wez Exp $ response_header("CVS Branches and how they relate to PECL"); ?> <p> If you have your PECL code in the PHP CVS repository, you need to be aware of our branching convention. The PHP core code is branched like this: </p> <pre> ------------------------------------ HEAD (development) \ \ \ ---- PHP_5_0 (stable) --- PHP_4_3 (stable) </pre> <p> All development takes place on HEAD, and important bug fixes are then backported to the stable branch(es) when appropriate. In general, no new features are added to the stable branches.</p> <p> The convention for PECL extensions is to use a similar (but not identical!) scheme, in order to more easily coexist with some magic in the repository and with snapshot building tools: </p> <pre> ------------------------------------ HEAD (development) \ \ \ ---- PECL_5_0 (stable) --- PECL_4_3 (stable) </pre> <p> You only need to create/maintain these branches if the PHP core is branched for release and HEAD (of both your code and the core) is changing in a backwards incompatible way, so that it would not be possible to compile your code against the release branch anymore. </p> <p> You <b>don't</b> need to branch if your code on HEAD has appropriate <tt>#ifdef</tt>'s to allow it to compile with the different PHP versions. </p> <p> You also don't need to branch if you don't intend to maintain your extension for those older versions; make sure you publish a version specific PECL package before dropping support for a release. </p> <?php response_footer(); ?>

« previous php.pecl.cvs (#1809) next »