Sorry about the delay. I was out of town most of last week. I've fixed the bind_meta_data problem and the tgsetup.py on Windows problems. Please give it a try and if all is good, I'll tag it.
My next step after that is to go through all of the 1.0b2 tickets in trac (paying particular attention to any patches in there) and decide which get applied. I'm going to move tickets around as needed to meet this goal: 1) get outstanding patches applied or rejected (or at least commented on, if changes are needed) 2) get a 1.0b3 out with that 3) see if there are bugs that absolutely must get fixed and work on fixing those 4) release a 1.0b4 with those fixes 5) 1.0rc1 if 1.0b4 is not broken 6) 1.0 final After that, we can schedule tickets for 1.0.1, etc. I just don't like making release candidates of betas. It also occurs to me that tgsetup.py can request a specific version of TurboGears, which means that one version of tgsetup can download the current release, the next one coming up, a nightly build, whatever... we can do some useful things with that. 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?hl=en -~----------~----~----~----~------~----~------~--~---
