Rattledagger
Elite Member
"We added a "milestone" field to Taskbase entries,
and assigned milestone values to all BOINC entries.
The current milestones are:
M1: public launch of SETI@home on BOINC
The major gating items are:
- No critical/high priority bugs in BOINC
- SETI@home failures under 5%
- preparations for increased server load
In this release, the client versions will be as they
currently are (GUI/screensaver for Win, CLI for Mac/unix)
M2: decommission old SETI@home
(i.e. turn off the current SETI@home data server)
The major gating items:
- Separate-GUI architecture
- GUIs available for Win, Mac OSX, Unix/X11
M3: support for Climateprediction.net and other projects
Gating items:
- client data management
- directory structure in project dirs
- WU interleaving
- trickle messages
- file compression
- support for non-CPU-intensive applications
We've tried to adhere to the following definitions of priority levels:
Critical
The bug would lead people to stop running BOINC, e.g.:
- it causes BOINC to stop doing work on a host,
even after a restart of the core client
- it causes the core client to violate user preferences
(use too much disk or network BW, etc)
- it is a security vulnerability
High
- It prevents a significant number of people from participating
- It causes recoverable crashes of the core client
- It significantly interferes with work getting done
- It gives zero credit in lots of cases
- Gating item for milestone
Medium
Strongly desirable new features
bugs that give too much or little credit
Low
Weakly desirable new features
cosmetic items
I've also tried to assign ownership of bugs either to the logical
person to work on the bug (not that they necessarily are doing so)
or else leave it "unassigned".
There are a few items that could be worked on by outside developers;
these are assigned to "Team".
-- David (Anderson)
For those who don't know where the taskbase is, it can be found here:
http://setiathome.ssl.berkeley.edu/taskbase/database.cgi
----- Rom (Walton)"
and assigned milestone values to all BOINC entries.
The current milestones are:
M1: public launch of SETI@home on BOINC
The major gating items are:
- No critical/high priority bugs in BOINC
- SETI@home failures under 5%
- preparations for increased server load
In this release, the client versions will be as they
currently are (GUI/screensaver for Win, CLI for Mac/unix)
M2: decommission old SETI@home
(i.e. turn off the current SETI@home data server)
The major gating items:
- Separate-GUI architecture
- GUIs available for Win, Mac OSX, Unix/X11
M3: support for Climateprediction.net and other projects
Gating items:
- client data management
- directory structure in project dirs
- WU interleaving
- trickle messages
- file compression
- support for non-CPU-intensive applications
We've tried to adhere to the following definitions of priority levels:
Critical
The bug would lead people to stop running BOINC, e.g.:
- it causes BOINC to stop doing work on a host,
even after a restart of the core client
- it causes the core client to violate user preferences
(use too much disk or network BW, etc)
- it is a security vulnerability
High
- It prevents a significant number of people from participating
- It causes recoverable crashes of the core client
- It significantly interferes with work getting done
- It gives zero credit in lots of cases
- Gating item for milestone
Medium
Strongly desirable new features
bugs that give too much or little credit
Low
Weakly desirable new features
cosmetic items
I've also tried to assign ownership of bugs either to the logical
person to work on the bug (not that they necessarily are doing so)
or else leave it "unassigned".
There are a few items that could be worked on by outside developers;
these are assigned to "Team".
-- David (Anderson)
For those who don't know where the taskbase is, it can be found here:
http://setiathome.ssl.berkeley.edu/taskbase/database.cgi
----- Rom (Walton)"
