Difference between revisions of "Alpha"

From CDOT Wiki
Jump to: navigation, search
(Issue description and/or number (2))
(Issue description and/or number (3))
Line 54: Line 54:
 
=== Issue description and/or number (3)===
 
=== Issue description and/or number (3)===
 
* Assigned to: [mailto:ssun24@myseneca.ca Shijie Sun]
 
* Assigned to: [mailto:ssun24@myseneca.ca Shijie Sun]
* Code review by: [mailto:ssun24@myseneca.ca Shijie Sun]
+
* Code review by:  
 
* Status:
 
* Status:
 
*: (being developed/pull request/being reviewed/pushed to master)
 
*: (being developed/pull request/being reviewed/pushed to master)

Revision as of 01:16, 8 November 2012

ALPHA

Project Marking Percentage

  • due immediately

Group work:      30%        (25 <= xx <= 50)
Individual work: 70% +      (50 <= xx <= 75) 
-------------------------
Total           100%

Repository

  • repo Github id:

Team Members

Team Name (team x)
First Name Last Name Section Seneca Id Github ID wiki id IRC nick Blog URL
Shijie Sun B ssun24 nihao123 Shijie Sun Jack Sun program344
Sivathanushan Easwaran B seaswaran sivae Sivathanushan Easwaran LineCircle OOP344Class
James Marmer B jmarmer jamesm007 James Marmer ToraReaper Blog
Ronny Wan B rwan3 ronnywan Ronny Wan ronnywann ronnywann
Jungmin Ji B jjungmin Ji Jungmin Ji Jungmin Viscaria Hit!

Issues and Status

Issue description and/or number (1)

Add console class to project and test with cio_test  (issue 1) 

Issue description and/or number (2)

  • Assigned to: Shijie Sun
  • Code review by:
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CField Mock-up Class (issue 2.1)

Issue description and/or number (3)

  • Assigned to: Shijie Sun
  • Code review by:
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CLabel Mock-up Class (issue 2.2)

Issue description and/or number (4)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CDialog Mock-up Class (issue 2.3)

Issue description and/or number (5)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CLineEdit Mock-up Class (issue 2.4)

Issue description and/or number (6)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CButton Mock-up Class (issue 2.5)

Issue description and/or number (7)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CValEdit Mock-up Class (issue 2.6)

Issue description and/or number (8)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CCheckMark Mock-up Class (issue 2.7)

Issue description and/or number (9)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
Add Text Class to the project (issue 2.8.1)

Issue description and/or number (10)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CText Mock-up Class (issue 2.8.2)

Issue description and/or number (11)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:
CCheckList Mock-up Class (issue 2.9)


example:

Issue description and/or number (2)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:

Coding Rules

meetings

  • latest will be on top
  1. topic and date1
  2. topic and date2

discussions

Question and discuss

  • Nothing for now...