On 09/03/15 13:47, Nicolas Morey-Chaisemartin wrote:
On 09/03/2015 08:37 AM, Maxim Uvarov wrote:
On 09/03/15 09:29, Nicolas Morey-Chaisemartin wrote:
Just a question a bit beside the point:
What is the policy about API-NEXT?
I was very surprised to see that the api-next branch was merged to master just
a few commits before the release.
I would have expected it to be merge right after v1.3.0.0 tag so we have a
fairly tested master being released, the new api changes being queued for the
next release and a new api-next branch ready for v1.5.0 API changes
Nicolas
1.3 tag was removed and will be retagged with that fixes. I.e. there is no 1.3
release yet. And that is one of main feature of 1.3. After that api-next will
be the same as before.
Maxim.
It's not a good idea to remove tags. All of us pulled the repo so we have our
own copy of the v1.3.0.0 tag and when you'll push the new one again, ours won't
move.
yes, I know. Please delete this tag. (there will be no api change from
previous wrong tag).
So you are saying that this pre-release api-next is a one time thing to get the
ordered queues merged in?
yes. It supposed that schedule tests were fine. But for some reason we
stuck at all that bugs. Only bug fixes to linux-generic implementation
and tests for scheduler are show stopper.
Maxim.
_______________________________________________
lng-odp mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/lng-odp
