Thanks for all the replies.
To summarise this thread, we have 5 people who agree with the proposals,
and also a few other points:
1. Attila - We should create tests to ensure the compatibility is not
broken accidently.
2. Pifta - We should emphasize JSON can allow fields to change order, and
any
Thanks all for the active discussion.
At present,The discussion was more in favor of delayed release. The main
reason is that:
1. Some features have been merged recently, we need a few weeks to fix
bugs, such as EC.
2. Many new features need improvement , such as EC needing Offline Recovery.
3. Th
Thanks Pifta for starting the discussion.
I think we can sum up your comparison of feature branch vs. master
development as: the problems we usually have to solve with feature
branches are procedural (busywork), while solutions required for a
comparable master-based model improve the product itsel
I've seen the feature flag pattern work successfully across large projects
many times. A long running feature branch is seldom worth the trouble it
brings with merge conflicts.
Once you've done it a couple of times, you start to realize that certain OO
tricks can make it easier as well - using fac