[Bf-committers] meeting minutes - June 13, 2010
ideasman42 at gmail.com
Tue Jun 15 13:33:31 CEST 2010
At the moment we don't have a clear owner of modifiers who has
authority to accept/reject patches in this area.
I could post a video and people might like what the modifier does but
I'm more interested in being able to get review on functionality and
Since there is no 1 person who is clearly the maintainer and modules
are becoming a large area how about we assign 3 module owners?,
We had this for python scripts in 2.4x and I think it worked well.
Each person should have written at least 1 modifier or done a
significant work on the modifier stack...
- Nicholas Bishop
(Brecht and myself would accept this role too)
On Mon, Jun 14, 2010 at 1:36 PM, Brecht Van Lommel <brecht at blender.org> wrote:
> On Mon, Jun 14, 2010 at 12:30 PM, revuedelibre . <revuedelibre at gmail.com> wrote:
>> Are we talking about bpy.ops.render ?
> This is about external render engine integration, not running
> executing a render from python.
>> For me, we can't remove features that was present from 2.4x
>> New version must have at least all features from old.
> 2.6 will miss some features that were in 2.4, if it's too unstable we
> should disable it. Discussed this with a Campbell, we agree that it
> can be marked as being experimental still, much like other parts of
> the API that have not been tested well, but it doesn't need to be
> disabled. The render API itself is very small and I can fix bugs
> reported with it, but most of the API is actually the same 2.5 python
> API as used for exporters and UI.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers