5 second executive update: 1.0 is coming. Still need docs.
Longer update: It seems like a good time to do a general project update, and clarify where people can help. The TurboGears 1.0 API is done. There may be some minor additions, but there won't be breaking changes between now and 1.0 final. I'm also working to ensure that only changes with minimal risk to production use are checked into the 1.0 branch. So, everything is organized around the notion that we are stabilizing things for a 1.0 release. (The trunk is open for business for riskier and bigger things.) There is work to be done in the code, but docs are key to being able to start down the beta path with 1.0. Some folks have volunteered to help with the effort. I'd love to do some of that myself, but I'm tied up in a big documentation project (the book) and, in a way, a smaller documentation project (the coming issue of o3 magazine). I'm pleased to announce a new mailing list for people working on (or desiring to work on) TurboGears documentation: http://groups.google.com/group/turbogears-docs Once everything is moved over and Docudo is the official repository for the docs, there won't be too much coordination necessary. But, I do think that now (and at various points in the future) there is a need for people to be on the same page with what work is being done. If you do want to work on some application-level code in TG, you can help out by working on Docudo which has shaped up quite nicely thanks to Ronald Jaramillo's efforts in recent times. If you want to help out in code for 1.0, take a look around the 1.0b1, 0.9 and 1.0 milestones in Trac. See if there's something in there that grabs you. There's a database error that comes up in Transaction.__del__ that is one I for sure want to fix before 1.0b1. Otherwise, any fixes are up for grabs. Do ask questions about any ticket if you're uncertain about approach or whether such a thing should even be done. I will try to sneak in a release of some sort this month. This month is really, really hairy for me. (If someone wants to volunteer to update the changelog, email me privately. That will make it faster for me to put together a release.) Once I'm back from EuroPython, I don't have any looming deadlines. Though my time will be limited by having a "regular job", I will not be in the midst of projects that are consuming my every waking hour (or so it seems at times ;) Kevin -- Kevin Dangoor TurboGears / Zesty News email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
