API feature?

[RussH]

@anonymoususer72041 the next PR up is the API feature, #703 if I look to roll this in, will it make all your subsequent PR's fail?

[RussH]

or are there some of your PR's you want to add in first as a priority?

[anonymoususer72041]

@RussH there are a few things we should consider regarding #703. I am still waiting for your answer regarding changing base branch from develop to master in this PR.

Generally I have no problem if other PRs get merged first but at the same time huge PRs like for example #703 should not block other PRs.

[RussH]

for the moment, I'm okay to change the target away from develop to master, however in general once we have a stable master I'd rather develop new features in develop and then merge it back for a release. i'll comment on the #703 and see if it needs repointed to Master, otherwise will ask the contributor to rebase and resubmit so I can do some manual testing

[anonymoususer72041]

Okay, in that case I would suggest you to sync develop with master before rebasing #703. Is there something that would get lost if we sync develop with master?

[anonymoususer72041]

Do you want me to change base branch of my PRs to develop branch?

[RussH]

no, I've rebased it - looks like this API PR is really against the Master codebase, as there's only two conflicts once it's repointed. the PR to merge develop back to master will be a challenge, will have to take a careful look.