[Bf-committers] 2.56-beta release AHOY!

[loopduplicate at burningtoken.com]

The process is already getting constantly refined and it can serve as 
model for other companies to follow when coming up with their own 
current best practices.  The process gets revised often because of the 
changing nature of the program.

People have tried to make automated processes in the past.  It's just 
next to impossible to come up with a solution that let's you build for 
all the platforms Blender works on.  Just ask the Graphicall folks who 
try to automate the building process.  It would require a team of people 
to develop and maintain.

On 12/30/2010 08:48 AM, Thomas Dinges wrote:
> The time and ressources needed for building/maintaining such an
> infrastructure is not worth the benefit.
>
> Our current process is much more flexible and proved to work well. :)
>
> Am 30.12.2010 17:44, schrieb kitt3n:
>> I think you guys are doing an amazing job - but I'm wondering why this
>> "building" isn't
>> handled by an automated buildserver (maybe with some virtual machines
>> for each of the
>> targeted platforms)?
>>
>> The entire process to get these versions out seems very error-prone with
>> long turn-around times...?
>> Are there practical reasons for doing it manually?
>>
>> Regards
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>