These problems existed for 4.4 and the same continued to 4.5. Despite discussing lot of things, we didnt act on anything and we are continuing the same to 4.6
There is no plan whatsoever to address any of those issues. ~Rajani On Wed, Nov 5, 2014 at 2:33 AM, David Nalley <da...@gnsa.us> wrote: > On Sun, Nov 2, 2014 at 11:40 PM, Rajani Karuturi <raj...@apache.org> > wrote: > > that means, we postponed the git problems to 4.6. :( > > > > It feels like as a community we are running away from making any changes > to > > the way we interact with git. We seem to discuss it a lot but, never act > on > > it. > > I don't think we are running away from them. I certainly hope not. > There are competing demands (like everything) > 1. We want to ship 4.5 > 2. We want to have new features being developed > 3. We want to fix quality issues > 4. We want to fix process issues > > Each of those is at odds with each other. They are also hard problems, > and frankly most of them are as much a cultural problem as a technical > problem. > > > > > What I don't understand is, are we saying the way we use git is right? or > > are we just shying away from any change? > > > > We are saying that #2 forced us to fork 4.5 into a different branch. > Master and 4.5 are now diverging, and we want to #1 to happen. 1 & 2 > are incompatible on the same branch, but their competition is keeping > 3 and 4 at bay. > > That doesn't mean we shouldn't change, but you can only pull in so > many directions without things coming apart. > > --David >
