I think we need to agree what should be part of this release.
3.5.1 should be a bugfix release, i.e. no completely new features, though
some minor improvements seem okay.
All regressions between 3.3.9 and 3.5.0 should be part of 3.5.1, because
new issues are in general easier to reproduce.
>>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
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
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?
(As usual, I have my own ideas but I will hold back until I see some
suggestions from others because we are a community and as release manager
for 3.5.1 my opinion might be too powerful and we
