50
edits
Changes
Jump to navigation
Jump to search
Line 128:
Line 128: − + + +
→About your project
Q.3 : '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''
Q.3 : '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''
Ans : '''TODO''': ''Make a timeline after discussions''
Ans :
As can be seen from the system diagrams above, 0.1 refers to the first Milestone which will be released as version 0.1. 0.3 to M2 which will be released as Ver 0.3 . 0.5 as M3 which will be released as Ver 0.5 . The point of making systematic releases in a period of 15-30 days each is to promote early testing and critcism of software. Also it helps since people can see working versions of the activity.
'''TODO''': ''Make a timeline after discussions''
----
----