johnf wrote: >>> Yea just like the event horizon to a black hole :-) >> Yep. And just like the elusive Dabo 1.0 - "real soon now". :) > All joking aside I believe Dabo (the framework) can be moved to .9 at this > time (or 8.5 if you wish). I see don't see any show stoppers and there were > several major changes including "prePK", parent->child->grandchild that have > been fixed. There are a few that have not been fixed - parent.rowcount=0 the > requery does not update the children, NonUpdateFields. I would like to see > DJ's patches (specially the tab order). But they are not required. > > I realize that it only been a short while since you released .8 but I see > Dabo > as already meeting the goals (as I understand them) set out for 1.0.
We need to get patches merged, review and close tickets, review where we are on the roadmap, etc. > To bring up a sore subject - how about calling the next release "unstable" > vs "stable". A "stable" release simply means that it isn't going to change. "unstable" is the trunk. It isn't a sore subject (at least not from my POV), but I'm sure it'll all make more sense after we are post-1.0. Our release strategy follows that of other open source projects, including that of Python itself. There's a set of prior stable releases, such as Python 2.5, and then there are the development releases, such as Python 2.6a1. The only thing we are missing is a beta/rc cycle prior to making a stable release. I assume we'll formalize that post-1.0. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
