>>Question is: How to decide which commits/JIRA issues will be merged to master for the next release?
Usually I respect the Jira priority, e.g. blocker or critical or I change the priority, and then those issues are preferable which necessarily must change the architecture first due to other Jira issues depend on it. Also change order of issues to what is more important for you from the point of future. You know what is the target you want to reach and thus you must have your own priorities. Step by step, you change something because you know what is best fitting to your development and what is the most simple for you. On Mon, Mar 20, 2017 at 2:36 AM, Christian Schulte <[email protected]> wrote: > Am 03/19/17 um 12:43 schrieb Stephen Connolly: > > So planning for 3.5.0 was total chaos... but it seems to have worked. > > > > How do we want to work for 3.5.1? > > We need to answer all the other questions first (versioning, bug vs. > feature, branches, etc.). Question is: How to decide which commits/JIRA > issues will be merged to master for the next release? > > Regards, > -- > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers Tibor
