Re: Validate_HU - don't do releases unless you commit the changes to cvs.

From: Date: Thu, 05 Feb 2009 10:30:34 +0000
Subject: Re: Validate_HU - don't do releases unless you commit the changes to cvs.
References: 1 2 3  Groups: php.pear.qa 
Request: Send a blank email to [email protected] to get a copy of this message
On Thu, Feb 5, 2009 at 3:03 AM, Joe Stump <[email protected]> wrote:
>
> On Feb 4, 2009, at 6:17 PM, Matthew Fonda wrote:
>
>>> If I haven't heard from either of you in the next few days, I'll pull the
>>> releases until the changes get into CVS.
>>
>> Don't get me wrong--I am definitely in favor of requiring packages to be
>> under source control, but I think until there is an RFC passed saying
>> packages are required to live in source control, I don't think you should
>> pull a release because it isn't.
>
> Matthew is right. Unless those releases are broken you've got no leg to
> stand on to pull the releases. It should be noted that Services_Digg has
> *never* been publicly available via a code repository (due to us wanting to
> keep new features under wraps while we develop them).

I was pretty sure that the group came to a conclusion about making
people have the code available in some of the 100 available free SCM
systems - except in situations like Digg where we get an explanation
and proper rationalisation for it.

Having commit history available and the source is very helpful, nay,
important for QA :-)

- Helgi


Thread (6 messages)

« previous php.pear.qa (#5200) next »