[Rspec-devel] process for introducing bigger changes

David Astels dastels at daveastels.com
Sat Jul 22 10:00:27 EDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 21-Jul-06, at 9:05 PM, Steven R. Baker wrote:

>> agree. anything big needs to be discussed first. big things are  
>> likely
>> to be put on a branch.
>
> I think an even better approach is to just put stuff on a branch.  No
> discussion required to create a branch.  This stuff is easier to talk
> about when it's somewhere that we can see.

+1

Dave

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEwi98auez/L4x7g4RAp5XAJ9JfCnfmifOfoCUy/HswiwleSqAwQCfXWPD
PuvQ44gWL5zUyKB3AnhiQ0E=
=AKDl
-----END PGP SIGNATURE-----


More information about the Rspec-devel mailing list