Reply to thread

Message

<blockquote data-quote="infinite.loop" data-source="post: 822009" data-attributes="member: 10723">I am sorry, but this makes perfect sense.In the past we had one bug/rework/feature delaying an MP release for 6+ months! This means that quite a few developers where sitting on their hands because the problem was in an area they had no idea about (i.e. SkinEngine), and due to the featurefreeze they could not work on anything else.By working in branches, we can fully test each change before it is added to the master/release. This means a change which has not been fully tested and approved will not get into the master anymore.Also developers can now work on their feature/bugfix/rework without being stalled by a featurefreeze that is active on the master.Yes, testing is more work. But in the end the stability and the overall development workflow/speed of MP highly benefits from this development model.Later on there will also be builds of the master (pre-alpha 1.3.0, pre-beta 1.3.0, pre-rc 1.3.0).But first the work in the branches must be finished before they can be merged with the master.This is how we work.</blockquote>

[QUOTE="infinite.loop, post: 822009, member: 10723"] I am sorry, but this makes perfect sense. In the past we had one bug/rework/feature delaying an MP release for [B][COLOR="Red"]6+[/COLOR][/B] months! This means that quite a few developers where sitting on their hands because the problem was in an area they had no idea about[I] (i.e. SkinEngine)[/I], and due to the featurefreeze they could not work on anything else. By working in branches, we can fully test each change [U]before[/U] it is added to the master/release. This means a change which has not been fully tested and approved will not get into the master anymore. Also developers can now work on their feature/bugfix/rework without being stalled by a featurefreeze that is active on the master. Yes, testing is more work. But in the end the stability and the overall development workflow/speed of MP highly benefits from this development model. Later on there will also be builds of the master [I](pre-alpha 1.3.0, pre-beta 1.3.0, pre-rc 1.3.0)[/I]. But first the work in the branches must be finished before they can be merged with the master. This is how we work. [/QUOTE]

Verification