Re: PHP Release Cycle

On Mon, 3 Apr 2000, James Moore wrote: >> normal bug tracking system, but keep a list of the important bug >> numbers and >> then email a list of these (in a similar format to the existing bugs >> summary) every day to the qa and dev lists. > >OK For now when we go into the release cycle if people can use the normal >bug system and then also post bug_id to QA with [RC_BUG] to the list Ill I think it would be good thing to add it into the bug report's subject line too (description?). Then they'll be easier to spot for example in listing of all open bug reports. [OT] Why isn't it (short desc) editable for at least 'Dev Modify' ?? I'll add it if someone doesn't have any good reason not to. Another thing I think needs to be changed are those status options for 'User Modify'. They don't need other options than 'Open' and 'Closed'. >keep an eye out for them and post daily reports of their status to the >lists. Ill talk to zak about what we should do about a RC Bug Tracker.. >Ie wether we need a new one or just an extension to the current one. I don't see any reason to separate them. ie. The 'PHP version' could have one more version in it..? Note: The 'Latest CVS' should be in the top. And it's missing 'Latest Snapshot' ? --Jani