Okay, so the current job is hurting me, and by extension hurting TurboGears. Does anybody have a different one? I've managed to make some progress, at the least, though not nearly as much as I'd like. Again
*What Got Done?* The CI testing has come along for the 2.1 series. We still have the issue with Python 2.4 compatibility, but with 2.1 we're pretty close. We do have some sticking points, though. I've now added jenkins to the resources page, and it's visible at http://jenkins.turbogears.org/ . Alessandro, I can agree with getting sqlalchemy-migrate into the quickstart. It's useful, and people will appreciate seeing it. However, if you check out Jenkins at http://jenkins.turbogears.org/ (specifically, check out this build log: ) you'll see that it definitely is missing the test cases that show it's properly ready for the users. Could you look into fixing this please? I'll also get to work on testing the other scenarios (mako, no sqlalchemy, etc), so that we'll hopefully get at least Python 2.6 fully tested this week. I'd love to see that circle turn blue, and the sky come out on that project. Would be really nice. *Where Are We Now?* 2.0 is working on Jenkins, as you can see. This enables us to finish fixing up TG 2.0.4. I'm trying to get 2.1 on Jenkins entirely before working on that code, though. We're debating about the status of TG 2.1 and Python 2.4. Any feedback would be most appreciated. TG 2.1 on Py 2.6, though, is just looking like we need to finish cleaning up our act. We're almost okay, we just need to get better. I also mentioned, earlier tonight, about me having devised a new tutorial application for the TG2 docs. Using this app, we can write up docs that will take users from a very simple application to a fully featured application running on mod_wsgi, etc. It's got a lot of potential. I'm calling it "job hunter". The basic idea is to have a site that hosts a resume. The resume includes everything, every bullet point ever used on a resume by a user. It includes all the skills, all the technologies, and all the projects, everything that the user can devise. Each item is then tagged by the user. For instance, I would add TurboGears as a technology. I would tag it with TurboGears and Python. At a later point, I can define a resume to include a predefined set of tags, and then generate the resume using those tags. The end result will be instantly customizable resumes for each and every job position being sought. It can store cover letters, records of when a resume was sent, to whom, provide follow up notices, etc. It's an application that is useful for showing how to do a large variety of things with TurboGears, and actual day to day real world use for users. By documenting the whole process, I can also revamp the TurboGears documentation to be up to date, correct, and much more useful. What do you all think? I like the app, and am writing it for myself, regardless. My question is this: Should I make it the official tutorial application? *What Will Get Done This Week?* I'm going to find a way to get 2.1 on 2.6 testing completed. We should have that much working flawlessly. I'm hoping to resolve the issue with 2.1 on 2.4 as well, though I'm not confident we can find a good solution for it. We might just have to go with the least crappy item. -- Michael J. Pedersen My IM IDs: Jabber/[email protected], AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen Twitter: pedersentg -- 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.
