Skip to content

Milestones

List view

  • Due by September 8, 2019
    2/2 issues closed
  • Due by August 31, 2019
    5/5 issues closed
  • Due by August 24, 2019
    9/9 issues closed
  • Due by August 17, 2019
    5/5 issues closed
  • Due by August 10, 2019
    2/2 issues closed
  • Due by August 3, 2019
    8/8 issues closed
  • Due by July 27, 2019
    3/3 issues closed
  • Due by July 20, 2019
    8/8 issues closed
  • Due by July 13, 2019
    5/5 issues closed
  • Due by July 6, 2019
    5/5 issues closed
  • Make all New Features work Smoothly

    Due by June 29, 2019
    13/13 issues closed
  • Due by June 22, 2019
    10/10 issues closed
  • Fixing Bugs and Preparing New Features

    Due by June 15, 2019
    7/7 issues closed
  • Getting started with PSLab

    Due by June 8, 2019
    8/8 issues closed
  • This milestone targets the completion of sensor integration with PSLab Android app. Following topics will be addressed. -- Uniform layouts in all sensor instruments -- Fix I2C read issues with communication modules in Android source code -- Test external sensors with the device

    Due by December 31, 2018
    10/11 issues closed
  • Once the milestone 2 is achieved, we will have; -- Functionality in Power Source, Multimeter and Wave Generator -- UI related to Multimeter and Logic Analyzer will be completed -- Merge development onto master and deploy app version 1.1.6 on Google Play

    Due by June 11, 2018
    11/11 issues closed
  • Once the milestone 1 is achieved, we will have; -- Completed UI designs and implementation on the app for (Oscilloscope, Logic Analyzer, Wave Generator, Power Source, Multimeter and Sensors) -- Completed structure of the app -- Merge development onto master and deploy app version 1.1.2 on Google Play

    Due by June 3, 2018
    18/18 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by September 10, 2017
    12/12 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by August 27, 2017
    19/19 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by August 20, 2017
    20/20 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by August 13, 2017
    24/24 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by August 6, 2017
    14/14 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by July 31, 2017
    13/13 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by July 23, 2017
    19/19 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by July 16, 2017
    14/14 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by July 8, 2017
    15/15 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by June 26, 2017
    6/6 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by June 19, 2017
    5/5 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by June 5, 2017
    5/5 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by June 1, 2017
    7/7 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by May 14, 2017
    5/5 issues closed
  • Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done

    Due by May 7, 2017
    5/5 issues closed