And just like that, we are on GitHub. Please ask here if you have trouble cloning or anything else.
Ongoing development will happen on the 'working' branch. Pulls into the 'master' branch will constitute new point releases and will automatically flow into web update releases, and new downloads from the dabodev.com download page. At this point I'm thinking we should ditch the Trac issue tracker and just use the simple one on GitHub to keep everything together. Opinions on that? Other options include upgrading Trac and setting it up against our Git repository or looking for other issue trackers. I have a strong hunch GitHub's is good enough. Paul On 1/5/13 1:50 PM, Paul McNett wrote: > Branch: refs/heads/working > Home: https://github.com/dabodev/dabo > Commit: 4dcbeb62ae9b6f5d4e64e2ca6f056ff343523a43 > > https://github.com/dabodev/dabo/commit/4dcbeb62ae9b6f5d4e64e2ca6f056ff343523a43 > Author: Paul McNett <[email protected]> > Date: 2013-01-05 (Sat, 05 Jan 2013) > > Changed paths: > M dabo/biz/dBizobj.py > M dabo/ui/uiwx/dGrid.py > > Log Message: > ----------- > Set implicit dColumn.Precision if bizobj-based. > > Since the decimal precision is already known in the bizobj, use that > for dColumn.Precision if the caller didn't explicitly set it. > > > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
