RE: [PEAR-DEV] Re: [midgard-dev] Re: [PEAR-DEV] Midgard in the sky with ... PEAR?
| From: | Lukas Smith | Date: | Sun, 27 Apr 2003 18:44:08 +0000 |
| Subject: | RE: [PEAR-DEV] Re: [midgard-dev] Re: [PEAR-DEV] Midgard in the sky with ... PEAR? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-15612@lists.php.net to get a copy of this message | ||
> From: Martin Langhoff [mailto:ml@nzl.com.ar]
> Sent: Thursday, April 24, 2003 11:25 PM
> - the CVS repository is _not_ PEAR, but project-specific
one thing that would be great however is to have all pear packages, even
if they are developed outside of PEAR to be in a cvs repository that
would send commit messages to pear-cvs. I think this is pretty critical
in order to prevent diverging efforts and for generally having a central
place to keep up on pear developments.
I don't know how easily this can be achieved with the currently used or
generally existing cvs commit mail scripts. But I think it would be
great if horde and midgard could set this up. Obviously we are only I
interested in the packages in your cvs that are pear packages and not in
the framework specific things.
Also we do have a few packages that are not in pear cvs that are
maintained totally separate (maybe even without any CVS) .. Var_Dump
comes to mind. Should we maybe make it a requirement for released
packages to be in some cvs repository? I wouldn't think that this would
be stepping on anyones toes, since we are not requiring it to be ours.
We just want to hear how development is going via the commit messages.
Regards,
Lukas