Davor Cubranic wrote:
Two of the nasties are mine, and I've been using a month-old build of Chandler until recently, when I upgraded it on one of the machines that I use but not the other. I wonder if it's the combination of using an ancient (as Morgen described it :-) client in combination with a more up-to-date one that's caused at least some of issues that I've run into.
Devs are pretty apt at spotting issues like this so I wouldn't say that this situation is creating bugs. It may surface some we wouldn't encounter otherwise but that's precisely why we value dogfooders so much... :)
Would you suggest keeping up with the most recent build at least every few days? Starting with a clean repo or keeping the old one if the schema hasn't changed?
I'd say do that on one of your machines. As you know, you don't have to start from scratch really. You can now export before switching into a chex file and reload your repo in the new release. This is pretty solid now.
Cheers, - Philippe _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
