Re: Re: getting a QA'ed package release

Let's put a BIG RED link to the making a release section with a STOP!! don't release until you have read this thoroughly or your release may be deleted without warning by the PEAR QA group. That should get everyone's attention :) Greg Lukas Smith wrote:

Stefan Neufeind wrote:

On 4 Mar 2004 at 13:02, Lukas Smith wrote:

It seems alot of people have a hard time to track the group announcements and more specifically the exact implications for their respective packages. This is all understandable and I am not trying to slap people for it. However I would like to encourage people to mail Pear QA if they are about to release a package so that we can have a quick look. Alot of the recent issues (like stable release below 1.0.0, not handling a BC break correctly) can be easily spotted.

How about the plans for maybe including a small "questionaire" in the upload-dialog, so it can automatically check which was the last release, which release was now uploaded etc. This way you could ask an uploader easily e.g. "does this release involve BC-break?" or "you can't release a stable - do a beta before" and similar. Also things like "tabs instead of spaces" or so could be automagically checked ...

Not sure about this. I think we should rather expand the "making a release" section that Tal started a while back. Essentially developers can then just open this guide and step through it one by one. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07