Speaking of which, I'm probably going to get together a Twisted Weekend soon focused on killing bugs and doing a 2.2. I was going to do it this past weekend, but didn't want to conflict with the doc-vsprint. How about next weekend, or the weekend after?
To be fair, the automation around actually producing tarballs for Twisted, all subprojects, and sumo is now pretty quick. There are still lots of problems around web site maintenance and documentation management (apart from the content itself), so that would be an excellent place to put your effort. On 1/16/06, Tommi Virtanen <[EMAIL PROTECTED]> wrote: > Andrea Arcangeli wrote: > > This is exactly the point. When a bug happens, there should be a stable > > release of twisted. As said above all twisted apps needs this, not just > > Nevow. > > Yes. I agree. That would be a lot better than any "epsilon" package. > > Clearly what the community needs is a more automated build process, so > we don't burn out our beloved Release Manager. Work on tools and > automation would be very much appreciated, I am sure. > I'd love to help but honestly don't have the time right now, I'm > too busy to release even the projects I do release manager tasks for :( -- Twisted | Christopher Armstrong: International Man of Twistery Radix | -- http://radix.twistedmatrix.com | Release Manager, Twisted Project \\\V/// | -- http://twistedmatrix.com |o O| | w----v----w-+ _______________________________________________ Twisted-web mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
