1) SCM validation Today SourceForge sent a notification to all wxCode developers to check as a precaution the SVN changes during the period when SF's servers were attacked.
As far as I can tell wxCode's SVN repository is intact. 2) CVS to SVN transition Today SourceForge informed also about the CVS service being back online - although still with some caveats. So I plan to prepare copying all wxCode components still residing in CVS to SVN in the near future to unify them in a single repository since up to now no wxCode developer objected to this step. 3) wxCode website SourceForge provides new web services for projects' websites and is currently moving all project webs to new servers. I'm going to check the wxCode website when it has been moved and to adjust the code if necessary. Please let me know if you discover any issues. I'll try to bring the wxCode website content up-to-date thereafter (i.e. making the registration of new developers and components more reliable), but this may take a while. Regards, Ulrich ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ wxCode-users mailing list wxCode-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxcode-users
