[Bf-committers] Freestyle branch review

Brecht Van Lommel brechtvanlommel at pandora.be
Wed Oct 24 19:15:41 CEST 2012


I think we discussed this sort of thing before. In my opinion, either
we support a feature officially or we don't. We'd still have to ensure
the data structures are designed so that they can keep working in the
future, we still would fix bugs, and need take the code into account
when refactoring, etc. Hiding it behind an addon wouldn't help much.
Maybe it gives us fewer bug reports because there would be fewer
users, but for me it doesn't really address the main reason why you
don't want to have all code from branches in trunk.


On Wed, Oct 24, 2012 at 7:01 PM, Tom M <letterrip at gmail.com> wrote:
> Brecht,
> could code be included but the UI be treated as an 'add-on'?  Thus we
> aren't committed to the UI and it can be evolved to be more 'blender
> centric' but users aren't required to download a seperate binary to
> work with the feature and developers can work off the main branch?
> LetterRip
> On Wed, Oct 24, 2012 at 9:20 AM, Brecht Van Lommel
> <brechtvanlommel at pandora.be> wrote:
>> Hi all,
>> I was asked to look into the freestyle branch, to see what needs to be
>> done to get it included in an official release. For those not familiar
>> with how it works, there is some documentation here:
>> http://wiki.blender.org/index.php/User:Flokkievids/Freestyle
> _______________________________________________
> 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