Companion Checklist
Rev. 1.01, 2006/07/13
Package Name: _____________
- What is the URL for the Open Source package?
How did you verify that you downloaded the correct bits?
md5sums?
2. Is this a new package?
If so, explain briefly why the package should be added
3. Under what license is the package distributed?
4. Have you made any changes to the the open source code?
If so, please provide details of the changes and the
reasons for them
Have your changes been accepted back into the main source
distribution?
5. Code review complete and all issues resolved?
Please list all participants in the code review
and describe briefly what was actually reviewed.
6. Describe briefly the testing you have done.
7. Bugs
How will bugs be tracked?
8 Dependencies
What other packages does yours depend on?
What packages depend on yours?
Please identify dependencies as build time or run time
9. Are manpages included in your delivery?
10. Packaging
New package name- Any setuid or setgid executables?
12. Does the software contain encryption?
if so, describe the type of encryption, key length, etc
(i.e type of encryption, key length, etc)
13. What's your current target integration date?
- Any setuid or setgid executables?
>
on 2009/10/26 12:12