Comments on: New Surfulater release, V2.00.10.0 ready and waiting http://blog.surfulater.com/2007/04/26/new-surfulater-release-v200100-ready-and-waiting/ Surfulater, the journey continues... Thu, 09 Feb 2012 01:22:49 +0000 hourly 1 http://wordpress.org/?v=3.0 By: My Cantina » Surfulater V2.00.30.10 Released http://blog.surfulater.com/2007/04/26/new-surfulater-release-v200100-ready-and-waiting/#comment-24570 My Cantina » Surfulater V2.00.30.10 Released Wed, 20 Jun 2007 01:58:48 +0000 http://blog.surfulater.com/2007/04/26/new-surfulater-release-v200100-ready-and-waiting/#comment-24570 [...] Surfulater V2.00.30.10 is the second of two releases in quick succession. With the V2.00.10.0 upgrade to enable multiple articles to be selected in the Knowledge Tree, Surfulater came out the other end a little worse for wear. I always knew that implementing multiple selection was going to be reasonably complex and impact on quite a number of areas, but I’m a bit annoyed with myself that two quite serious issues slipped through testing. The fact that they took a while to surface is some small conciliation, however it would of course been far better for everyone if they hadn’t existed in the first place. The most serious problem was fixed in V2.00.30.0 which has been out for almost a week now and the folks that had reported the problem have not had it reoccur so far. [...] [...] Surfulater V2.00.30.10 is the second of two releases in quick succession. With the V2.00.10.0 upgrade to enable multiple articles to be selected in the Knowledge Tree, Surfulater came out the other end a little worse for wear. I always knew that implementing multiple selection was going to be reasonably complex and impact on quite a number of areas, but I’m a bit annoyed with myself that two quite serious issues slipped through testing. The fact that they took a while to surface is some small conciliation, however it would of course been far better for everyone if they hadn’t existed in the first place. The most serious problem was fixed in V2.00.30.0 which has been out for almost a week now and the folks that had reported the problem have not had it reoccur so far. [...]

]]>