[Windmill-dev] List policy

[Mikeal Rogers]

One of the biggest problems right now is that we're encouraging users  
to use the trunk. The trunk, by definition, is subject to changes  
like this.

I agree with a policy where changes to externally facing interfaces,  
APIs , windmill binary name or options, etc. should be sent to the  
list before commit on trunk for those using and developing on the trunk.

But in the future we shouldn't have _any_ changes like this during  
maintenance releases, and we should provide proper migration support  
when possible.

This week we should be pushing out a release candidate for 0.2. After  
that, any 0.2.x releases shouldn't contain _any_ changes to public  
facing code. All of those changes need to be in 0.3.

-Mikeal


On Oct 1, 2007, at 11:41 AM, 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