[Bf-committers] PyAPI breakage and possible solutions

Campbell Barton ideasman42 at gmail.com
Thu Jun 17 21:38:48 CEST 2010

Talked with Brendon and Luca, we agreed addons can just be checked
before release and we can contact their maintainers to fix bugs, fix
ourselves or in worst case move to a different svn location,

On Wed, Jun 16, 2010 at 11:44 PM, Matt Ebb <matt at mke3.net> wrote:
> On 17/06/2010, at 04:27 , Campbell Barton wrote:
>> I'm not really interested in mailing list discussion on this topic, We
>> can agree addons for release must be stable.
> +1
> * Releases must be final and stable
> * SVN is for development not for use, there should be some expectation that things may break (which can ideally be reported and fixed)
> And the big one that I can't emphasise enough:
> * If addons are going to be included in Blender as part of official releases, they should also adhere to Blender's development cycle (feature freeze, stabilisation, release notes).
> Otherwise they should have their own development cycle, not bundled with blender, but available as a separate download and managed as separate projects.
> Matt
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

- Campbell

More information about the Bf-committers mailing list