When those have been resolved, I'm planning to wait 5 days for the dust to settle and possibly some lower priority low hanging fruit to be committed.
Then, I want to release 1.5.0-rc2 (hopefully by the end of next week).
My plan is to branch the 1.5 branch just before the release and create the release off of that branch. The branch point marks a moment where contribution to 1.5 will more strictly be measured against the following criteria:
* No new features (in the application; development framework/tests is fine)
* Contributions must be stabilizing
* All PRs for the 1.5 branch will be strictly reviewed
By going this route, I want to "free up" master for the great new ideas that come in almost on a daily basis through Matrix and IRC, while still being able to stabilize 1.5 and being able to make the 1.5 release in the not-too-distant future.
Comments?
--
Bye,
Erik.
Robust and Flexible. No vendor lock-in.