Andrew Boon
We do plan to approach it in a slightly different way. Dolphin 8 should have separate updates for modules that would come out as soon as even small bugs are fixed. This would allow separate parts that need to be updating and the core won't have to be updated too frequently. Much like when you update iPhone OS every few months and apps as soon as their updates are available.
Andrew Boon
Just wanted to add that frequent updates of the core is not a good idea - simply because we don't want to keep people updating their sites every day.
dolphin_jay
Well thats sort of the point i was trying to make with rebuilding the dolphin707.zip every time a bug was fixed in svn. When a new user comes to boonex and downloads the zip file it would have the new bugs fixed in it. That way only a handful of people would need to update there sites...

You could also place an update tab in the new studio and have it check the svn for REV. # for new fixes and have it wget the new fixed files and rename the old files it replaces and let the users pick if they see more want to update or not.... But now that i think of it while writing this it has nothing to do with the topic so i'll leave it at that.
Andrew Boon
Unlike desktop app or very simple web apps, Dolphin is very sensitive to server setup, so auto-update for the entire system would fail very often. I'm not ruling out this opportunity, but we'll start with separate module updates first.
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.078771829605103