I supose it'll be a collection of all fixed done in the svn beta versions
That's basically it - just sanity checking all the stuff that's been committed to svn and bringing it together to make a complete package. V130 will be a full setup too, not just an update. I've already updated the demos and everything seems to be working well.
Syncmods may be disappearing in 130 - just have to check with Brucey if he's still using it for his own stuff (Brucey?). V1.30 Maxgui module will be distributed via a zip file from the product updates page. 'Bleeding edge' updates will continue to be available via SVN.
I may put together a little svn tool for those who are having problems here - but honestly, it's not THAT hard! Just install SVN and go...
svn checkout http://blitzbasic.com:81/svn/blitzmax/dev/main c:\blitzmax
svn checkout http://blitzbasic.com:81/svn/blitzmax/dev/win32_x86/bin c:\blitzmax\bin
svn checkout http://blitzbasic.com:81/svn/maxgui/dev/maxgui.mod c:\blitzmax\mod\maxgui.mod
...which effectively 'copies' svn files to your computer. Then to sync with any updates...
svn update c:\blitzmax
svn update c:\blitzmax\bin
svn update c:\blitzmax\mod\maxgui.mod
...and rebuild modules if necessary - ie: if anything in 'mod/' was updated.
The main trouble with syncmods was it really just introduced another point of failure. Not only did I have to deal with keeping 4 (platform) copies in sync via svn, I also had to do the same with syncmods (which wasn't that smart and required manually updating version numbers) - mess up one step, and suddenly there's a ton of unhappy users with link problems and so on. It effectively created 8 versions of Max too - the 4 I'm working with via svn, and the 4 available via syncmods - it was nuts! Also, it couldn't handle anything not in /mod/, like the compiler, bmk etc.