[Rspec-devel] process for introducing bigger changes

Brian Takita brian.takita at gmail.com
Sat Jul 22 00:49:53 EDT 2006

I agree.

On 7/21/06, Steven R. Baker <srbaker at pobox.com> 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.
> -Steven
> _______________________________________________
> Rspec-devel mailing list
> Rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/rspec-devel/attachments/20060721/172da114/attachment.html 

More information about the Rspec-devel mailing list