[Windmill-dev] List policy

[Matthew Eernisse]

Adam,

Actually my commit was a new feature needed to make Cosmo's unit tests 
run under Windmill's JS test framework. But I agree with what you're 
saying.

I'll make a point to send an e-mail proposal to the list if I'm going to 
do anything that might induce breakage in the app, or in people's 
existing tests.


Matthew


Adam Christian wrote:
> I move to make it a requirement to send an email to the list before you 
> do a checkin that might break other peoples stuff. I just saw a commit 
> from mde because my commit to rip out the iframe required him to change 
> code in the js testing stuff.
> 
> Obviously, "I fixed a typo" doesn't merit an email but in the next 
> couple months I have a feeling there will be a fair amount of 
> architectural changes to piece of our code base, and since our community 
> is already starting to grow we need to keep the communication channels 
> clean.
> 
> I know I have seen Mikeal do this a few times, but everyone else 
> (especially me) needs to get on this train as well. Ideas?
> 
> Adam
> _______________________________________________
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/windmill-dev
>