Skip to content

Milestones

List view

  • Due by November 27, 2017
    1/1 issues closed
  • Due by November 13, 2017
    6/6 issues closed
  • Due by November 6, 2017
    16/16 issues closed
  • Due by October 23, 2017
    8/8 issues closed
  • Due by October 2, 2017
    2/2 issues closed
  • Due by September 15, 2017
    2/2 issues closed
  • Due by September 11, 2017
    3/6 issues closed
  • Let's keep this an a container for all issues that have to do with second step of CI/CD (first was to integrate with cocoapods), which is integrating with Travis CI. The goal here is to have successful builds at Travis, together with basic integration testing on the simulator, Reference Doc generation, etc

    No due date
    9/9 issues closed
  • Due by November 11, 2016
    14/14 issues closed
  • Interim release to add H264 and UI changes

    Due by October 26, 2016
    10/10 issues closed
  • Due by May 17, 2016
    80/80 issues closed
  • Due by October 12, 2015
    88/88 issues closed
  • Due by June 10, 2015
    16/16 issues closed
  • Mainly stability fixes and enhancements for this release

    Due by August 23, 2015
    62/62 issues closed
  • Placeholder for items too far to be assigned to a regular release

    Due by April 30, 2016
  • There's a lot of work involved in proper packaging of iOS SDK, let's create a milestone as a container for the issue involved. What is involved roughly: - Better organize repo. Currently there are includes outside of the repo (which only work in my machine) - Web RTC build I'm currently using is huge (and resides ourside the repo). Check if we can find a smaller one and introduce it in the repo so that developers can readily use it. - More organization in the repo. For libs we use for which there isn't a separate dir introduce one with the usual structure (i.e. include dir with all includes plus .a lib) - As an enhancement we could consider producing iOS frameworks as well -although they might cosiderable effort to produce - Consider producing a CocoaPod for the needed libs. - After all is ready we also need to automate production of libraries as possible so that we can make new releases with minimum effort.

    Due by May 28, 2015
    83/83 issues closed