Okay, so I put together a very preliminary schedule, which has the tools
putback happening in early May. Details are on the project web page:
http://www.opensolaris.org/os/project/scm-migration/scm-mig-schedule.pdf
Some assumptions:
- I'll be working 50% on technical issues and 50% on technical project
management issues (mostly reviewing/updating documentation and tool
status).
- I made a random guess and put down Jim C working 25% on technical
issues.
- I put down Rich as 100%. (Enact only knows about people with SWAN
accounts, so I used the "Engineer" role for him.)
I'm actively looking for feedback in these areas:
- Are there things on the list that we don't need to do? I'm willing to
drop items from the list (after discussion), but I'm not willing to
reduce effort estimates until we have a track record of meeting
existing estimates.
The effort estimates for bugs include the P1-P3 bugs in the bug
list--the first "bugs" link on the project task list page[1]. If
you're looking at one of those bugs and trying to make sense of the
comments, post to scm-migration-dev and we'll try to clean it up.
The effort estimate for bugs do *not* include the hg_trans bugs in
Bugster. I plan to fix that next week (see the "bug review" task).
- Are the effort allocations for me and Jim correct?
- I need a better understanding of how we'll be doing testing. Will Jim
Walker be running tests for us, or will the developers being doing all
the testing? And we need to finalize the test plan.
Other comments:
I think we want to tackle the hg fixes, and any other high-risk fixes,
soon.
mike
[1] http://www.genunix.org/wiki/index.php/SCMMigrationTasks
