[Windmill-dev] Release process going forward

[Mikeal Rogers]

I'm getting fairly annoyed with how long it's taking us to release 0.2.

We're going to have bugs in whatever we release, the trick is to have  
a good plan in place for bugfix releases and new work going forward,  
which we don't have.

Here is what i propose as a plan for 0.X.x bugfix releases.

  * Automated "push button" build/verifcation/unittest and upload to  
PyPI ( I already have one such script for functest ).
       -- This means that if a fix is important we can push a release  
in minutes.
  * Every bugfix has to be checked in with a unittest.
  * EVERY BUGFIX HAS TO BE CHECKED IN WITH A UNITTEST
       -- The only way we're going to reduce the chance of  
regressions is to require that bugfixes have unittests checked in and  
slowly improve our coverage.
  * If there have been any checkins at the end of the week and we  
haven't already pushed out a release that week we'll just take the  
changes that did make it in and push out the 0.X.x release.

What we have been calling "0.3" should be called "0.Twisted". The  
bucket for 0.3 service work is too big and there is a good amount of  
service work that all depends on each other. This doesn't leave much  
room for an interim release with IDE features that will get  
accomplished in the interim.

All feature work will be done in branches going forward, when we feel  
some of these features are ready we'll merge them in to trunk and  
push a 0.X release.

Questions? Comments? Hate Mail?

-Mikeal