I moved from the old dedicated server to a slightly more powerful one.
The process was painless for existing users and I doubt anyone really noticed the transition except if using DNS servers that are not updated often enough.
Though, mail distribution from the redmine platform was disrupted for a while and no registration/notifications could therefore be done/sent.
This is now resolved, apologies for the inconvenience.
QtCreator-Doxygen: Mac binaries ready for testing (3 comments)
I just uploaded a build of the plug-in for Mac users, seems to work well at least with binary Qt Creator 2.1.0 from Nokia when running in 64-bit.
Should work equally well in 32-bit but it is untested yet. Should also work with the SDK but untested as well.
So grab it, test it, and please tell me how it works for you :)
If you do want to monitor the activity of the project in terms of scm commits please do not do it like a freak or all you'll get is a nice place in my firewall drop table.
I mean, hell, it's perfectly fine to check every couple of hours or so but every minute is just asking to be kicked to death. It's not like it was a massive project with huge activity.
It's not the first time I have to deal with such behaviour but at least I could contact the people involved directly (company) now for individuals, asking an ISP to pass the message on is like peeing against the wind, that won't be done.
So in other terms, use atom feed(s) or slack on the svn up stuff or you'll be banned.
If everyone using this project was doing an svn up every minute, the server would greatly suffer from this, I can't accept that.
After cleaning up apache and its modules, I actually broke svn permissions for non authenticated users and you couldn't checkout the repository. This is now fixed. Silly me.
I removed the binaries for 2.1.0-rc1 because they could go into an infinite loop on not so uncommon code and, well, that's just bad isn't it?
It should be fixed in commit r37 but I don't think I will bother creating and uploading new binaries until 2.1.0 is finally out which should be imminent, anyway.
Sorry if you run into this bug while doing productive work guys.
Also available in: Atom