Toolchain roadmap for the dapper+1 release
The toolchain should be speced one release in advance so the following release opens with the correct and tested tool chain. This would include having a tested version by preview freeze, so we can do a test rebuild of the archive before the next release opens. I.e. have stack protection ready for 2005-04 (compiler, glibc (backports), other things ...).
Blueprint information
- Status:
- Complete
- Approver:
- Jeff Bailey
- Priority:
- Medium
- Drafter:
- Matthias Klose
- Direction:
- Needs approval
- Assignee:
- Matthias Klose
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Matthias Klose
- Completed by
- Matthias Klose
Whiteboard
Review Comments:
maybe needs update after the toolchain roadmap for dapper is spec'd and approved
Approver Comments:
I have placed my comments in the spec and put this back in draft. Please keep in mind that someone not present may want to participate in implementing it, so the spec should have as much detail as possible. Also, in cases where things are outstanding, please indicate why they're outstanding, and why they can't be resolved at UBZ.
Estimated Developer Days
- preparation of toolchain packages: 7, 5 done
- test rebuild, evaluation of rebuild (developer, buildd admin, admin) 5-10
- preparation of glibc+ssp packages: 8
- preparation of packages to start with in dapper+1: 4
20060706 doko: set status to implemented; all toolchain parts did land in edgy