Hello, I tried to actually check, which patches are sitting in the api-next. And actually I failed to do that in a timely manner. git cherry produces a list of patches, that contains a lot of patches, which already landed to the master.
Quick proposal would be to stop using api-next as a long-lived branch which received updates from master and rather use it as a branch being regularly rebased on top of current master. Another possiblity would be to abandon api-next completely, develop features on topic branches, which get merged to master, rather than to api-next. At least this would save us from situations, when there is API definition (or change), but no actual implementation behind. -- With best wishes Dmitry
