Re: new maintainer Re: [PEAR-DEV] Re: [ANNOUNCEMENT] System_SharedMemory-0.0.4 (beta) Released.

Lukas Smith wrote:

I dont think this necessarily needs to be the case for the first set of alpha releases at the beginning. Then again its very important that the directory stucture and file naming is done right at the beginning, since this can hardly be changed in CVS.

Agreed.

Well the learning curve in PEAR development is not exactly steep imho, but it is there. I think as long as the package is in early alpha the developer can one by one work through things.

From a personal point of view I'd opt for immediate adheration, but I'm fine with that since it has been clarified now ;) I would add a constraint to it though: with the releasing of a package with beta state, all PCS must be complied with!

We might also add an entry to the new maintainer guide "your first release: a checklist".

That's a very good suggestion!

Some of the regulations are also missing from the manual. I just opend a bug report on this.

Thanks.

Finally we might consider sending an email to all new developers which points them at the "new maintainer" guidelines and welcomes them to the team.

Again, excellent idea. -- Stefano