[Bf-committers] Roadmap for 2.5x - 2.6x - beyond
gustav.goransson at gmail.com
Mon Mar 14 15:48:01 CET 2011
I'm not a coder, but I guess one issue is to determine weather a
branch is stable or not, and to know if it have been properly tested.
Why don't do this in a more systematic, 'official' way than before:
When a branch is getting near completion:
1. Set up a dedicated bug tracker for the branch, provide builds and
do an official 'Call for testing' announcement at Blender.org
2. Give it some time, and when the tracker is consider stable enough
do the merge
In this way you'll get a lot more user involvement and help to
identify bugs before a merge to trunk I guess...
On Mon, Mar 14, 2011 at 13:47, Thomas Dinges <blender at dingto.org> wrote:
> Big -1 for this,
> seriously let's not change the naming again!
> Ton and others decided on naming it 2.57 and 2.58 (Ton sent a mail with
> this in January to the ML). Let's stick to that!
> This is the n'th discussion about it on this list, and it starts to get
> annoying. ;-)
> Am 14.03.2011 11:02, schrieb Jonathan Smith:
>> I think this will also make more sense to developers, in that we have 2.60
>> as the base and we start working up and adding stuff from there,
> instead of
>> working from 2.58 up to 2.60 and having a bunch of new features in 2.60.
>> Just my two cents,
>> Bf-committers mailing list
>> Bf-committers at blender.org
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers