Crash関係:
SHA-1: 4503f82ba2734c6d1830d367e1d52a5ce21d2491
* Fix T38312: Crash when using snap transform in edit mode
　Issue was caused by uninitialized boolean flag.

SHA-1: 94325035f4fa0c45885194efb16eebc1af0d2d65
* Fix T38298: crash saving float image with 3 channels from exr to png/jpeg.

SHA-1: 2a7665697637810515fb3620dad19c72f1c13e13
* Fix T38295: Crash when changing screen with different visible layers
　The issue was caused by missing object update for the curve object
　before going to new screen. And that new screen had different visible
　layers due to disabled lock_camera_and_layers option.
　Solved by calling DAG_on_visible_update() in ED_screen_set() even
　in cases scene doesn't change. This ensures all the objects which
　weren't visible before are correctly updated.


気になったもの:
SHA-1: 28ca299d4dfc392462efd598f14b825ba8bd21ea
* Fix T38316: Half of a Face is Missing on Newly Created Cubes or Cylinders.
　Own bug from rBc691551249f3. Now at least I understand why `test_index_face()` is needed for tessellated quads!
　Added a bunch of comments to explain the issue, as it's far from an obvious one...
　We loose some performances, but it's still much quicker than org code.

SHA-1: c691551249f3fe3982c43e4c75be40a19503dd26
* Optimize tessellation code (min 20% better, up to 300% with some CD layers to tessellate).
　The main idea is to store (during tessellation) or recreate (during tessdata update) a tessfaceverts-to-loops mapping,
　and then update all tessdata
　in one pass, instead of calling `BKE_mesh_loops_to_mface_corners` repeatedly for all tfaces!

今回は長文の解説文が多いです。
Crash関係:
SHA-1: 0f72a8a7f0a0f8fff11ee26859c33ab684d6e19b
* Fix T38337: Crash when calling to_mesh() on a Curve object after clearing its parent
　This is rather a workaround which only works because curve evaluation is only called
　for a temporary object. Not a big deal if we'll skip path creation for such objects.
　Still would need to think of general solution.

SHA-1: 26ae14d2dccd0d34edfe9f26a4126e9a69e74983
* Fix crash when changing space type to 3D space when having multiple windows
　it is possible that different windows shares scene but displays different
　layers. And it's also possible that different areas in the same window will
　show different layers.
　First case was violated in `dag_current_scene_layers()` which only checked
　scene layers only once and if multiple windows shares the same scene only
　one window was handled. Now made it so layers from all windows will be
　squashed together into a single `DagSceneLayer`. This mainly solves issue
　with `DAG_on_visible_update()` which didn't work reliable with multiple
　open windows.
　Second case required call of `DAG_on_visible_update()` when changing space
　are type.
　This commit slows things a bit actually because `dag_current_scene_layers()`
　is actually called on every main WM loop iteration. It is possible to speed
　some logic up perhaps. Not sure it's so much critical to do now because there
　are unlikely to be more than few windows open anyway.
　Will rather think of skipping all that flushing things if no objects are
　tagged for update actually.

SHA-1: 64bd4be6b2d9d093c56e6cce809d8cd1650ebe6f
* Fix for crash getting the name of RNA properties with empty name

SHA-1: cbdedc169dd948d308dcdb1fc2e74b1fdd25880c
* Fix T38284: Crash with several shrinkwrap constraint using same target
　Issue is caused by the race condition between getting custom data layers
　from target's derived mesh (for vertices and faces) and releasing this
　derived mesh from other threads.
　When one releases the derived mesh it'll free temporary data from it,
　and it'll also update data layers mapping.
　General rule for threading is that no one is ever allowed to modify
　data he doesn't own. This means that no temp layers are to be allocated
　in derived mesh and making it so `CustomData_free_temporary()` doesn't
　update mapping if nothing was freed will solve the race condition.
　It is still possible to do other improvements, namely detect which
　additional data/layers are to be present in derived mesh and create
　it as a part of `object_handle_update()`, but this is to be solved
　separately.

少し意味合いが異なりますがCrash関係ということで・・・
SHA-1: 4b820fb673319989026433f284e11671885757c0
* Fix T38311: cycles BVH cache crash on Windows.

Crash関係:
SHA-1: bb83bdf89123690e99ef36afd24a93246685dc68
* Fix T38366: export collada crash - if you set a keyframe
　Don't assume all objects have a valid animdata...

SHA-1: c0a40892652e89601060a9590ea0a6f0606d28bb
* Fix T38356: Crash when UIList.filter_items returns too few items.

気になったもの:
SHA-1: 67f1fd25ee6361df5f84e254eea103fe7952125f
* game engine: implement hitMaterial for collision and ray sensors

Crash関係:
SHA-1: 21c56f754fd60ae82fc42a1f781afecde5227282
* Fix T38355: Crash with Shader Node Group with missing datablock,
　only in "Material" viewport shading.

Crash関係:
SHA-1: 1c0cdc385f68f3714fbf087acfb2696ee1c8383d
* Fixes for keyframe selection
　Using tracks with constant zero weight used to crash
　keyframe selection since it was trying to use missing
　parameter blocks for Jacobian evaluation,
　Also fixed possible issues with wrong camera block being
　marked as variable. This could technically happen when
　having zero weighted tracks. Made it so all camera blocks
　are marked as variable for now.

気になったもの:
SHA-1: 9178dc9d384f18ab2f23656fb6b01a3b444526ef
* Rework detector API and implement Harris detector
　Switch the detector API to a single function which accepts
　a float image and detector options. This makes usage of
　feature detection more unified across different algorithms.
　Options structure is pretty much straightforward and contains
　detector to be used and all the detector-specific settings.
　Also implemented Harris feature detection algorithm which
　is not as fast as FAST one but is expected to detect more
　robust feature points. It is also likely that less features
　are detected, but better quality than quantity.
　Blender will now use Harris detector by default, later we'll
　remove FAST detector.

SHA-1: 2b858b45c26b52cdbf80528b6445248adc8eb7f1
* audaspace: use new libavcodec audio encoding API where available

SHA-1: f99e581ae13c2c563f66cb0c31d3dfceeec21af7
* libavformat API usage: use avformat_close_input() instead of av_close_input_file()

SHA-1: 414e40c353cad08493e90585cd1261297c96570f
* libavformat API usage: use avg_frame_rate instead of r_frame_rate
　r_frame_rate is a guessed number defined as "the least common multiple of
　all framerates in the stream". It has been deprecated and removed in new
　Libav releases.
　Use avg_frame_rate instead, which is the average framerate of the
　stream.

SHA-1: b7f8bfef2506dfd44d638e2280f00e301823fb2c
* libavcodec API usage: use new video encoding API
　avcodec_encode_video() has been replaced with avcodec_encode_video2()
　in new libavcodec versions.

SHA-1: 8fa4517a208127e1773c21382deb1e8844ffdc9b
* BGE: remove freestyle from stubs, all functions were out of use

いや、この記事はこっちの事のようです。

Blender Institute Announces Blender Cloud Plans

BlenderNationの記事です。

Crash関係:
SHA-1: dd684f5a0414e9f2882a4861de489e50ea1ddb2e
* Fix T38400: crash in image_listener accessing deleted object.
　Listeners should never dereference this pointer because the object may have
　been deleted, it can only be used for comparisons.

Crash関係:
SHA-1: 2011156eec720a01088bc0bd02bd4021e39d7c65
* Fix for crash linking node groups through bpy.data.library
　Defer creating the Python objects until after appending is finished
　because NodeTree's types are not initialized until then.

SHA-1: 2b55d7895ced2c737e827e6a808634f730d275fc
* Fix T38403: Laplacian smooth on instanced objects leads to crash.
　The laplacian modifiers (smooth and deform) use the OpenNL library,
　which is not threadsafe due to the use of a global context variable.
　Ideally this would be changed so that an explicit context can be
　created for every caller of the OpenNL functions, but since OpenNL's
　most recent version is from 2010 this is unlikely to happen.
　As a workaround for now just use a mutex to prevent conflicting OpenNL
　calls. Eventually OpenNL can be replaced by eigen or ceres.

Crash関係:
SHA-1: 482823a1abc4e1fae7d010940b6b4bc867205f0d
* Fix T38435: Crash when pressing MMB in walk mode
　Snap code may be called with a NULL region, add check about this and assume ray_start is OK in this case!

気になったもの:
(というか、最近掲示板に投稿があったのでそれ繋がりということで・・・)

SHA-1: a16998911b59956806000826c15a941c53bd33c1
* Freestyle: Fix for iterations over 0D elements in the reversed order.
　The revision is concerned with Interface0DIterator and StrokeVertexIterator.
　These iterators can be generated by Interface1D::vertices_end() and
　Stroke::stroke_vertices_end(), respectively. These methods return an
　iterator poinitng the next index of the last 0D element (i.e., iterator's is_end
　property is true). When the iterators created in this way are used with
　Python's iterator protocol (e.g., in a for-loop), iterations over 0D elements
　are automatically performed in the reversed order. This functionality was
　broken after recent revisions concerning Freestyle iterators.
　Also made minor code cleanup (white space).

ビルド情報とは関係ないですが・・
何気にアニメの再生速度が若干向上したような気がする・・。
(ここ数週間の修正で何かあったかな?・・・)

メモリーリーク:
SHA-1: 6a2c467443f9d6d47fc9727457459a8ed92f1961
* Blenderplayer: Fixing a memory leak.
　IMB_moviecache_destruct() was not being called.