Overall, I'd say this was a decent week. Not perfect, and I think there's some more infrastructure changes that have to be made very soon, but still decent.
*What Got Done?* I got to work on continuous integration tools. I began with buildbot, but the number of problems I ran into due to lxml was too great. Even though it's still up and running, it's going to come down, and soon. Luke has had a Hudson (now Jenkins) instance running for quite some time. It even had things configured for working on TG2.0/TG2.1. We just weren't aware of it, and weren't using it. I've managed to get three (out of seven) TG2 projects up and running so far on it. I haven't attempted any of the TG1 projects, and I'll address that question momentarily. As part of the Jenkins configuration, I had to do some minor tweaks to branch-2.0 (tg), and to tg-docs. Things got updated, and minor incompatibilities introduced. That's what the testing is for, though, so we know what works and what doesn't. We also had an issue with the main website. On Thursday, the site was completely hung for about an hour. It looks like Paster's threads were locked up. A simple restart of Paster fixed the issue. I've since configured the server to restart Paster on a daily basis, so as to try to take care of performance issues that build after Paster has been running for a while. *Where Are We Now?* Continuous integration testing is one of the last pieces of our infrastructure. Once we have this in place, we've got our act together on the infrastructure, and it's just code and docs that have to get rolled out. As it stands, we can at least take care of 2.0. You can check out the results (so far) by visiting http://jenkins.turbogears.org/view/TurboGears%20Hosted/ The site is serving up data. It looks good, and we've even had people complimenting us on Twitter (Alessandro, would you mind posting the link here?) *What Will Get Done This Week?* That Jenkins instance still requires a little bit of tweaking. Once it's done (and I'm working with Luke on this), we'll have build results being posted to the ML. We'll all be able to see, very clearly, the current process of getting new code up and running. My primary goal is getting this done. I want to improve outside visibility into the current status of the code. Time permitting, I will also get 2.0.4 out this week, which we've been promising to our users for over a year. Only have to fix a couple of bugs on it now, at least. Christoph, once we get the Jenkins instance working the way we expect it to, would you mind working out the details of getting TG1 projects properly building there? I'd like to have all of our projects showing up properly. -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
