Re: Re: cvs: pear /HTTP HTTP.php package.xml

["Tomas V.V.Cox" <cox@idecnet.com>] > Stig Sæther Bakken wrote: > > > > > > Here's what I have in mind (dropping the V_ for now): > > > > RELEASE_1_2 Simple tag that can be used to check out the package > > in the state it was when {version} was released. It > > should not move. > > > > QA_1_2 Branch. Like PHP's release candidate branches, this > > branch is used to prepare a release, only critical > > bug fixes go here. Most people will not need this > > one I guess. > > > > MAINT_1_2 Branch. Let's say you fix some bad bugs in 1.2 and > > want to release 1.2.1 quickly, but there are some > > changes on the main trunk that have not been well > > enough tested. Make a MAINT_1_2 branch from > > RELEASE_1_2, commit the fix there and tag/release > > RELEASE_1_2_1 from the branch. Probably only needed > > for bigger packages with many developers. > > > > DEV_feature Branch for developing "feature" without interfering > > with the main trunk. > > > > > Stig, why not put the final decition about this and the examples you > gave on how to do it (cvs commands) in a doc? (user-cases.txt?) I have put it into the PEAR Coding Standards part of the PHP Manual. - Stig -- Stig Sæther Bakken <ssb@alltheweb.com> Fast Search & Transfer ASA, Trondheim, Norway