[Bf-committers] Blender 2.72 RC1 release AHOY!

[Sergey Sharybin]

Hey,

We're ready for first release candidate in the 2.72 release cycle.

Information for platform maintainers:

- Branch: blender-v2.72-release
- Branch hash: eb464eed57e695594c1e8c6738c27a6b7846d657
- Locale hash: 841b1b9f494b6f980da4e244bbd86ecb8a8ac0b7
- Addons hash: fd695c3a81b63db072311e8516e0dbb8d4474047

In order to update the git this magic sequence should work:

- git pull
- git checkout blender-v2.72-release
- git submodule update --recursive

Just to verify it's all fine (it's first time we release from Git tags).
Your head is to be eb464eed57e695594c1e8c6738c27a6b7846d657, and
`git submodule` are to show:

 841b1b9f494b6f980da4e244bbd86ecb8a8ac0b7 release/datafiles/locale
(v2.72-rc1)
 fd695c3a81b63db072311e8516e0dbb8d4474047 release/scripts/addons (v2.72-rc1)
+c74ea88ca1aa9fa12be348cbdb17926c1426b8d9 release/scripts/addons_contrib
(heads/master)
 625d446ae8996ff1b3d660c44e2827fc832cf12b scons (heads/master)

Please note, it is a REAL release candidate. Meaning, if we do a fix, we
backport it to the branch and do another RC.

I would also ask to explicitly specify fixes which are to be backported,
that'd save us quite reasonable amount of time.

Also please note Git is considered frozen for until all the builds are up
(approx ~24hrs from now on). No commits are allowed to the master branch
for until unfreeze message is sent t this ML (expect this tomorrow
afternoon).

Keep usual naming of the archives and have fun! Thanks everyone for this
release cycle!

-- 
With best regards, Sergey Sharybin