I'd like to thank the developers for this release… Lots of nice things. I've been waiting for the ffmpeg in Windows for some time to make life easier for my students. Now we can do it all in Blender! (once I figure out this crashing issue or change our process)

Anyway, for those people who have unanswered questions/concerns…

@andiK:
It's just you – try resetting the cache in your web browser as it might be interfering with more up-to-date versions of the page.

@Höhrer:
If you detail the problem and provide a bug report the script or blender are more likely to be fixed – also, if it's the script that's at fault (which is what it sounds like) then it's just a simple matter of downloading an older version of the script that did work and putting that in place the current one packaged with blender and fixing any compatability issues that arise. (there shouldn't be anything major) If you still can't fix the problem, I might be able to help since I can code reasonably well in python – although I don't know about the md2 file format. If, on the other hand, the problem is with blender, I still might be able to help but as I'm not (yet) as good at C as I'd like, I might not – however, you can give me a try as I'd love to feel useful and it might inspire me to learn C properly and contribute fixes/features to blender. My email address is 90mins.tdk*a*googlemail.com+ (simply replace the *a* with an @ sign and remove the trailing +) if you want to contact me. On the other hand, you could just as easily ask the script author or maintainer as I'm sure they'd be more than able to help or you could contact some developer of blender (via the bug tracker) if it really is a bug!

@Daniele:
Yes, it's a bug – sculptmode should be faster now. (it could be your graphics drivers though perhaps)
Anyway, the blender bug tracker can be found by going to http://projects.blender.org and clicking on the link that says "bug tracker". Alternatively, you can just go straight to: http://projects.blender.org/tracker/?atid=125&group_id=9&func=browse
The second one is quicker but the first one is more reliable if the site changes in future. One day the web site maintainer will fix it so that you can just go to projects.blender.org/bugtracker but at the moment it won't work. That's if you haven't found it already of course!! ;)

@gord and Renato Perini:
The source code can be found at: http://www.blender.org/download/source-code/ or by following the little link at the very bottom of the main page at http://www.blender.org that says "Source Code" under the heading 'Download' – the reason for this is that the main site has only quite recently been redesigned so as to be more user friendly and look more asthetically pleasing. Unfortunately, the source code link has become a little bit less obvious – maybe it should have it's own box on the download page (just a suggestion – this is OSS after all!) – unfortunately, I'm not sure who to mention this to as there are several people involved with the maintenance of blender.org; perhaps Bart since he did the Typo3 integration – then again, equally, Matt Ebb or anybody else who was involved (and has time as well – an uncommon commodity among blender developers!).

@Zxayant:
I think this project is on hold (as mentioned above) but I'm not sure how much time zaz and/or genscher actually have – or whether they will be able to finish the project at all. Anyway, as the softbody code is becoming more robust and able to simulate cloth resonably well and probably better in future it is doubtfull whether it will ever make it.

@panzi and Digital FX Artist:
AFAIK, pyNodes are still in development and should be in the next release of blender. There is a patch on the patch tracker if you wanted to build a version with them included although the code in development has changed a bit since it was put up I think – best to wait until it becomes available in CVS. (or SVN – whichever comes first lol!) The wiki page at http://wiki.blender.org/index.php/BlenderDev/PyNodes has been updated a lot by Nathan recently and I think he is focusing on the ShadeInput part so that scripts can actually get access to the internal data that would be required for python shaders to function correctly – somebody please correct me if I'm wrong! Also, there are testing builds at http://www.graphicall.org that contain pyNodes if you want to check them out although I'm not sure if there are any recent builds.

@JimC:
Unfortunately, I don't run windows so I can't say; but if you have a problem that is caused by blender, feel free to post it on the blender bug tracker. Or attempt to fix it yourself first!

@Neuralize:
I don't know about the shiny buttons – it could be that Snark hasn't finished them or that he hasn't put the patch on the patch tracker – etc etc… just because they were featured on blendernation doesn't mean they'll make the official release – for now, just cross your fingers and hope!!

Anyhow, it's a great release and the new features that have crept in can only do more to promote blender as free open source software over it's commercial rivals!! :) – and a very big well done and thank you to all the developers who helped to make the realese what it is!!
-epat. :)