Re: Branching PHP6

On Sat, Apr 5, 2014 at 10:32 AM, Stas Malyshev <smalyshev@sugarcrm.com>wrote: > Hi! > > > the gap only widening as time goes forward, it becomes increasingly > > difficult to quickly locate active branches of development. There's > > Here's the algorithm: active ones are named "master" or have one dot in > them. How hard is that? That putting aside the fact that there's not so > many of them that a person smart enough to write code that should be > committed to PHP repository wouldn't be able to just remember them. > > In short, I'm not sure I see what advantage spending time on removing > the branches give us. Their cost is zero, while our time costs more than > zero. > There are more active branches than that. For example the two str_size_* branches. Sometimes people also commit other work in progress branches. A github fork of a semi-active PHP core developer likely has at least ten additional "active" (as in, not yet merged) branches. I think keeping around dead branches does have a cost. It blows up branch listings significantly. If you open the branch list on github and try to find something you'll end up scrolling through more than fifty release branches and other dead ends. Nikita