[Bf-committers] Blender 2.71 RC1 release AHOY!

Ton Roosendaal ton at blender.org
Thu Jun 12 20:27:20 CEST 2014


For me you don't need to retag for adding the splash, but I would really insist on including the 271 splash in the builds. It's what we agreed on, and it makes the "RC" feel attractive and a real release.

We only have three people building releases, they can update with the splash i guess. :)


Ton Roosendaal  -  ton at blender.org   -   www.blender.org
Chairman Blender Foundation - Producer Blender Institute
Entrepotdok 57A  -  1018AD Amsterdam  -  The Netherlands

On 12 Jun, 2014, at 18:41, Sergey Sharybin wrote:

> Hey!
> With some delay we're now officially doing Release Candidate "The One" for
> 2.71 release! (well, 2.71-rc1 seriously speaking :)
> Information for platform maintainers:
> - tag: v2.71-rc1
> - don't think it's needed to bother with more hashes here
> Here's the magic command sequence which i believe will work for you
> $ git pull
> $ git checkout v2.71-rc
> $ git submodule update --recursive
> Just to verify it's all fine, check `git submodule` output and check that
> locales and addons points to v2.71-rc1.
> Use the following name: blender-2.71-RC1-<platform>
> Also please note Git is considered frozen for until all the builds are up
> (approx ~24hrs from now on). No commits (especially witespace/cleanup
> commits!) are allowed for until unfreeze message is sent t this ML (expect
> this tomorrow afternoon).
> -- 
> With best regards, Sergey Sharybin
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list