Hi David, On Tue, Jul 22, 2014 at 2:42 PM, David Soria Parra <dso...@gmx.net> wrote:
> > > > Even if we have PHP-5.7 branch, we have merge up policy. Therefore, > > any new feature will end up with master, I suppose. If a new feature is > > only available to PHP-5.7 branch, it's a merge bug, isn't it? > > > > Regards, > > We had this policy before and it didn't help us. The problem is > maintiaining all the branches and keeping people interested in the next > branch because people tend to focus on the currently release branch. > When we decided upon the release RFC we talked a lot about the overhead > of maintaing multiple branches and tried to reduce the amount of > branches. In particular with API changes it becomes tidious if we try to > maintain a feature across branches and that implicit divergence has to > be resolved better sooner or later, or otherwise it would be just like > the old php6 again. I can understand your concern. We have git now and git can easily spot what and who haven't merged required changes to master. Working with multiple branches and merge is much easier with git also. I think this time it will work, hopefully. My concern is development time. It's too short. We only have about half of a year to feature freeze. More than a year would be appropriate for a major version up, IMHO. Long alpha/beta period is good for users also. Having PHP-5.7 is not a mandatory, but I would like to have it. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
