Re: Importing packages into CVS

Alexey Borzov wrote: > Hi, > > Greg Beaver wrote: >>> My suggestion is to give a developer some limited time for pulling the >>> release (like a week, two weeks at most) since the problems warranting >>> said pull are usually quite obvious. And let's remove that "Delete" >>> button except for the packages that don't yet have any releases. Our >>> main goal is to ensure that whatever was released via PEAR stays there. >>> >>> Of course deleting the packages will still be possible with the help of >>> the admin, but I hope our admins learned that lesson already. :) >>> >>> So what I propose is writing guidelines for deleting packages / releases >>> and making changes to pearweb to enforce these. >> >> These are *excellent* suggestions. Would you mind writing up a draft >> for guidelines? I would like to see this implemented very soon. > > Yes, I'll do the draft. Should I create an RFC or a post to pear-dev is > sufficient? Yes, mailing pear-dev will be just fine, and once any potential tweaking is finished, I will be happy to docbook-ize it. > Although I doubt that even Christian is some kind of superhero able to > work on all packages at once. ;] Thus my suggestion on importing the > packages to CVS only when some actual work is to be done on them still > stands. This makes sense. As far as I can see, Christian has done this for a few packages that have open bugs, but he can answer to that question. As far as I'm concerned, if someone is willing to do the work, I support it :). Greg