is doing what is meant to do, no assumptions. When things break, it narrows the search; allowing fixes to be developed more quickly. Ensure that the changes haven’t broken any other existing functionality are appropriate in the level of testing. Previously, tests were created ad-hoc, based often on bug fixes, so did not extensively test the code. It was decided that we would develop a test-framework to there are a number of advantages that come from building from source. Avoid having to wait for bug fixes from full releases Building the latest version to test compatability early Testing new features

doing what is meant to do, no assumptions. • When things break, it narrows the search; allowing fixes to be developed more quickly. • Ensure that the changes haven’t broken any other existing functionality are appropriate in the level of testing. Previously, tests were created ad-hoc, based often on bug fixes, so did not extensively test the code. It was decided that we would develop a test-framework to there are a number of advantages that come from building from source. • Avoid having to wait for bug fixes from full releases • Building the latest version to test compatibility early • Testing new features

doing what is meant to do, no assumptions. • When things break, it narrows the search; allowing fixes to be developed more quickly. • Ensure that the changes haven’t broken any other existing functionality are appropriate in the level of testing. Previously, tests were created ad-hoc, based often on bug fixes, so did not extensively test the code. It was decided that we would develop a test-framework to there are a number of advantages that come from building from source. • Avoid having to wait for bug fixes from full releases • Building the latest version to test compatability early • Testing new features

is doing what is meant to do, no assumptions. When things break, it narrows the search; allowing fixes to be developed more quickly. Ensure that the changes haven’t broken any other existing functionality are appropriate in the level of testing. Previously, tests were created ad-hoc, based often on bug fixes, so did not extensively test the code. It was decided that we would develop a test-framework to there are a number of advantages that come from building from source. Avoid having to wait for bug fixes from full releases Building the latest version to test compatibility early Testing new features

system, shape keys, fur with particles, fluids, and rigid bodies. 2.41 -- January 2006: Lots of fixes, and some Game Engine features. 2.42 -- July 2006: The nodes release, Array modifier, vector blur light scattering beneath the surface of organic and soft objects. 2.45 -- September 2007: Serious bug fixes, with some performance issues addressed. 2.46 -- May 2008: The Peach release was the result of improvements in the animation system and the GE, vertex weight groups modifiers, 3D audio and video, and bug fixes. 2.61 -- December 2011: The Cycles renderer was added to the trunk, the camera tracker was added

system, shape keys, fur with particles, fluids, and rigid bodies. 2.41 – January 2006: Lots of fixes, and some Game Engine features. 2.42 – July 2006: The nodes release, Array modifier, vector blur light scattering beneath the surface of organic and soft objects. 2.45 – September 2007: Serious bug fixes, with some performance issues addressed. 2.46 – May 2008: The Peach release was the result of improvements in the animation system and the GE, vertex weight groups modifiers, 3D audio and video, and bug fixes. 2.61 – December 2011: The Cycles renderer was added to the trunk, the camera tracker was added

system, shape keys, fur with particles, fluids, and rigid bodies. 2.41 -- January 2006: Lots of fixes, and some Game Engine features. 2.42 -- July 2006: The nodes release, Array modifier, vector blur light scattering beneath the surface of organic and soft objects. 2.45 -- September 2007: Serious bug fixes, with some performance issues addressed. 2.46 -- May 2008: The Peach release was the result of improvements in the animation system and the GE, vertex weight groups modifiers, 3D audio and video, and bug fixes. 2.61 -- December 2011: The Cycles renderer was added to the trunk, the camera tracker was added

system, shape keys, fur with particles, fluids, and rigid bodies. 2.41 – January 2006: Lots of fixes, and some Game Engine features. 2.42 – July 2006: The nodes release, Array modifier, vector blur light scattering beneath the surface of organic and soft objects. 2.45 – September 2007: Serious bug fixes, with some performance issues addressed. 2.46 – May 2008: The Peach release was the result of improvements in the animation system and the GE, vertex weight groups modifiers, 3D audio and video, and bug fixes. 2.61 – December 2011: The Cycles renderer was added to the trunk, the camera tracker was added

system, shape keys, fur with particles, fluids, and rigid bodies. 2.41 – January 2006: Lots of fixes, and some Game Engine features. 2.42 – July 2006: The nodes release, Array modifier, vector blur light scattering beneath the surface of organic and soft objects. 2.45 – September 2007: Serious bug fixes, with some performance issues addressed. 2.46 – May 2008: The Peach release was the result of improvements in the animation system and the GE, vertex weight groups modifiers, 3D audio and video, and bug fixes. 2.61 – December 2011: The Cycles renderer was added to the trunk, the camera tracker was added

system, shape keys, fur with particles, fluids, and rigid bodies. 2.41 -- January 2006: Lots of fixes, and some Game Engine features. 2.42 -- July 2006: The nodes release, Array modifier, vector blur light scattering beneath the surface of organic and soft objects. 2.45 -- September 2007: Serious bug fixes, with some performance issues addressed. 2.46 -- May 2008: The Peach release was the result of improvements in the animation system and the GE, vertex weight groups modifiers, 3D audio and video, and bug fixes. 2.61 -- December 2011: The Cycles renderer was added to the trunk, the camera tracker was added