search for: pr14233

...eworking of core APIs was mixed with updating their consumers, and with general cleanups. This makes isolated reverts impossible, and general reverts increasingly hard as time passes. 5) There is at least one serious bug with the methodology being employed in some of the usage patterns, leading to PR14233. 6) Micah is out of the office for a while and not likely to have the time necessary to address these issues quickly. 7) We're going to be branching for 3.2 in not-too-long. When you combine all these factors, the best option I saw was to back out the widespread changes outside of the core...

...mixed with updating their > consumers, and with general cleanups. This makes isolated reverts > impossible, and general reverts increasingly hard as time passes. > > 5) There is at least one serious bug with the methodology being > employed in some of the usage patterns, leading to PR14233. > > 6) Micah is out of the office for a while and not likely to have the > time necessary to address these issues quickly. > > 7) We're going to be branching for 3.2 in not-too-long. > > > When you combine all these factors, the best option I saw was to back > ou...

...xed with updating their > consumers, and with general cleanups. This makes isolated reverts > impossible, and general reverts increasingly hard as time passes. > > 5) There is at least one serious bug with the methodology being > employed in some of the usage patterns, leading to PR14233. > > 6) Micah is out of the office for a while and not likely to have the > time necessary to address these issues quickly. > > 7) We're going to be branching for 3.2 in not-too-long. > > > When you combine all these factors, the best option I saw was to back >...