[PHP-DEV] Re: [PHP-QA] RFC:PHP Release Cycle From: Zak Greant (zak <email protected>)
Date: 11/08/00

Hi James,

Unfortunately, I could not do a thorough review of your RFC. However,
given that there have been no replies to it yet, I felt that I had to give
you some feedback. :)

I have taken the RFC and structured it as it made most sense to me.

I have also taken out the information on how the codebase is managed for
the RC process. The developers have had this discussion several times
already - they will have to arrive at their own solution (hopefully without
bloodshed :)

Perhaps this simplified format will make it more likely that people will
comment.

HTH,

Zak

RFC: PHP Release Candidate Evaluation Cycle
-------------------------------------------
Developers start thinking making a release.

Notification of the upcoming release sent to the DEV and QA lists a week
prior to first RC.

The DEV/QA teams gear up for the RC process.

The current codebase is <TBD> (branched, frozen, deep-fried, whatever
solution the developers arrive at...)

The RC is rolled and made available for testing.

The RC is tested.

RC bugs and successful builds are tracked. (Ideally via a build tracker and
RC-specific bug tracking method. This can be done manually if need be til
a solution is built.)

Process for dealing with bugs in the RC
---------------------------------------
Bug submitted along with support data. (Configure log, test script,
php.ini, support library info, etc...)

Bug validated by QA/DEV teams.

If bug can/must be fixed for upcoming release:
        Bug is added to RC bug queue.
        Regression test for bug written (as per php4/tests/README)
ELSE:
        Bug is added to normal bug queue.

Process for resolving bugs in the RC queue
------------------------------------------
Bug fix attempted.

If bug cannot be fixed, move bug to normal bug queue.

If bug fix is attempted, apply regression tests and have the bug submitter
confirm that the fix works.

Dealing with additional RCs
---------------------------

If bugs are found in the first or previous RC then another RC may need to
be rolled. The above process is repeated with the new RC.

What Happens to the codebase?
-----------------------------

<TBD>

The Final Release
-----------------
The DEV/QA teams should review the RC bug queue to make sure that all bugs
have been dealt with.

The Final Release is rolled and released. 

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>