RE: [PEAR-DEV] Image_Text mess in CVS
| From: | Stefan Neufeind | Date: | Wed, 12 Nov 2003 23:05:56 +0000 |
| Subject: | RE: [PEAR-DEV] Image_Text mess in CVS | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23560@lists.php.net to get a copy of this message | ||
On 12 Nov 2003 at 21:35, Lukas Smith wrote:
> > From: Martin Jansen [mailto:mj@php.net]
> > Sent: Wednesday, November 12, 2003 7:41 PM
> >
> > On Wed Nov 12, 2003 at 10:4734AM +0100, Bertrand Mansion wrote:
> > > Could the QA team (do we have a QA team BTW ?) have a look at the
> > > mess
> > in
> > > CVS with Image_Text and try to fix that ? Or would Tobias be nice
> > > enough
> > to
> > > look at other packages in CVS and try to do the same when
> > > committing,
> > and
> > > not invent its own way. Thanks,
> >
> > I agree. Cvs.php.net is a repository for a *big* number of
> > developers and we simply can't afford going with more than one
> > directory structure there. The current one has been there for years
> > and it seems to have worked out for most people in pretty much the
> > same way than the Tabs-vs.-Spaces issues did.
> >
> > In my not so humble opionion the benefits of adding a new structure
> > is out of all proportions to the wtf-dr [1] factory.
>
> I don't think it takes more than 3 seconds to figure out if a package
> uses the "new" directory structure.
>
> I also think that it adds significant comfort for a lot of developers
> that can now develop directly in their CVS dir. More importantly the
> random "helper" or "tester" can just run a properly prepared test or
> example directly out of CVS .. I am sure that will help to reduce the
> barrier for some early tests without going into the entire package
> release process.
Lukas, would it be possible that you bring this proposal up in the
PEAR group and let us know what they think? Generally I like the idea
Tobi had by just introducing a new hierarchical level. And although
Archive_Tar was not intended like it is now in my eyes it shows how
nice a package like this can look.
Personally I won't change my CVS-structure "radically" till tomorrow.
But Tobi's solution might make life a bit easier. And if PEAR group
agrees maybe they could come to a "suggestion" how to do it - not a
rule - let current developers in CVS decide for his own, sure.
And for those who want to change it would be helpful if somebody with
direct access could offer to move their few directories without
actually loosing the CVS hierarchy.
Regards - and thanks for your support in this topic
Stefan