05-10-2015, 07:46 AM
(This post was last modified: 05-10-2015, 07:47 AM by LogicParrot.)
Well, this was talked about in the post discussing versions and branches but I thought I should mention it:
The new dev cycle that was talked about is this:
Master ---> Testing ---> Stable
Minor bugs and features go into master, only important fixes go directly into testing, once testing is stable for a while, testing becomes stable, master becomes testing.
I created an "Important" tag in Github, it is meant to mark the fixes that should go directly into testing, these are typically crash-fixes and other critical stuff. All features not marked with "important" should go to Master. I hope you guys are ok with this.
Ideally, Testing should never become "stable" until we have no more "important" tagged issues for a while. Feel free to tag anything you think it must make it to the next stable.
I hope you're all ok with this.
The new dev cycle that was talked about is this:
Master ---> Testing ---> Stable
Minor bugs and features go into master, only important fixes go directly into testing, once testing is stable for a while, testing becomes stable, master becomes testing.
I created an "Important" tag in Github, it is meant to mark the fixes that should go directly into testing, these are typically crash-fixes and other critical stuff. All features not marked with "important" should go to Master. I hope you guys are ok with this.
Ideally, Testing should never become "stable" until we have no more "important" tagged issues for a while. Feel free to tag anything you think it must make it to the next stable.
I hope you're all ok with this.