1. 1 March 10, 2008 1 Project Planning William Cohen NCSU CSC 591W March 10, 2008

2. 2 2 Planning ● Give people idea where project is headed ● Goals/deliverables for project ● Scope amount of work in project ● Have ready list of items for volunteers to work on ● Scheduling: ● When different phases of release happen ● What features will be in project

3. 3 March 10, 2008 3 Project Direction ● Most of the software projects are evolving ● Project plan describing what future features envisioned: ● Some features might just be wild ideas (long term) ● Other features very concrete (short term)

4. 4 March 10, 2008 4 Goals/Deliverables ● Particular features or functionality may be needed by project users ● Often project version number changed with major functionality additions

5. 5 March 10, 2008 5 Different Levels of Planning ● Informal: ● ToDo file in project or on Wiki or webpage ● More Formal: ● Road Map showing what features available and when

6. 6 March 10, 2008 6 When to Release ● Some projects use timed releases: ● Fedora release about every 6 months ● Release based on particular feature inclusion

7. 7 March 10, 2008 7 Scheduling ● Packages will have phases (e.g. GCC and Linux Kernel): ● Early phases allow significant changes ● Later phases only bug fixes ● Make it clearer when deadlines are coming up ● Motivate people to get their changes/fixes in by particular time

8. 8 March 10, 2008 8 Fedora Development States ● Development freeze ● Feature freeze ● String freeze ● Translation freeze ● Test freeze ● Release ● Final Development freeze

9. 9 March 10, 2008 9 GCC Develop States ● Each state about 2 months in duration: ● Stage 1: all changes allowed ● Stage 2: no major merges from other branches ● Stage 3: only bug fixes or new ports. No new functionality

10. 10 March 10, 2008 10 Complications ● Many Open Source Software project volunteer run ● Not clear when some features will be completed