On 26 October 2015 at 11:20, Wallen, Carl (Nokia - FI/Espoo) < [email protected]> wrote:
> Hi, > > It seems that also the odp-master branch contains api-changes even before > a new release is tagged? > Currently it's getting challenging to include the latest v1.3.0.0 bug > fixes into an external odp-based application when the odp-api also changes > underneath. > > What is the correct way to include only the bugfixes following an > odp-release and update the used odp-api only when the next release version > is ready/tagged? > Master is currently frozen and merged with api-next a week before release, no branches are made. The SC specify when there should be long term support for a version and then a branch would be made, effectively master is staging for the next release. The current description is here http://www.opendataplane.org/api-documentation/release-plan/ and we can amend it if there is a proposal. > > /carl > _______________________________________________ > lng-odp mailing list > [email protected] > https://lists.linaro.org/mailman/listinfo/lng-odp > -- Mike Holmes Technical Manager - Linaro Networking Group Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs
_______________________________________________ lng-odp mailing list [email protected] https://lists.linaro.org/mailman/listinfo/lng-odp
