> What should we do for the debugbar? > Should we release an alpha with TG2.1.4 even though it requires a > custom release of ming or should we wait for a new ming release? > (My patch for Cursor hooks has been merged, but a new release might > not happen soon).
You could test for the version of Ming and disable the feature if not the needed version or you could leave Ming from the debugbar out for this version and release a new one when Ming is ready, tough although if debugbar release is tied to tg release it may not be possible to go with the last option. > Does anyone know if there is any known issue for TG with SQLA0.7? > The debugbar requires it to work and I tested it only on simple > projects (slightly modified quickstart), > most of my big projects are already on production and so still use 0.5 and 0.6. I have been using SQLA 0.7 in some projects and haven't found any problems. -- 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.
