SFWNV C-Team Checklist
Rev. 2.05, 2007/04/04
Completed checklist should be sent to sfw_cteam-ext@sun.com.
Project Name: Squid Cache
(if your project name is a code name, please include a single-sentence
explanation as to what it is)
1. Project Inception
1.1 Why do you want to integrate through the SFW Consolidation?
Squid is an Open source package, The WebServer Apache which operates
in the same domain as Squid is in the SFW. So it seems like SFW is
appropriate.
1.2 Are there any other Consolidations that might be appropriate?
No.
1.3 Does your project conform to Software Big Rules and Solaris PAC
Policies? See http://solaris.eng/SOE/Solaris-PAC/policies/
Yes.
1.4 What are the Key Requirements for your project?
Squid is a fully-featured HTTP/1.0 proxy.
2. Review
2.1 ARC approval status: list case name, number, date approved and
approved release binding.
APPROVED - WSARC/2007/554 - Including Squid Cache 2.6STABLE16 with Solaris
closed approved fast-track 10/10/2007
Minor Release Binding
None 2.2. List all ARC TCRs and TCAs
- have they been resolved? (attach email with resolution)
Y 2.3 Code review complete and all issues resolved?
Please describe briefly what was actually reviewed.
update: usr/src/Targetdirs
update: usr/src/cmd/Makefile
update: usr/src/pkgdefs/Makefile
create: usr/src/cmd/squid/Makefile.sfw
create: usr/src/cmd/squid/install-squid
create: usr/src/cmd/squid/squid-2.6.STABLE16.tar.gz
create: usr/src/cmd/squid/Solaris/http-squid
create: usr/src/cmd/squid/Solaris/http-squid.xml
create: usr/src/pkgdefs/SUNWsquidr/Makefile
create: usr/src/pkgdefs/SUNWsquidr/copyright
create: usr/src/pkgdefs/SUNWsquidr/pkginfo.tmpl
create: usr/src/pkgdefs/SUNWsquidr/prototype_com
create: usr/src/pkgdefs/SUNWsquidr/prototype_i386
create: usr/src/pkgdefs/SUNWsquidr/prototype_sparc
create: usr/src/pkgdefs/SUNWsquidu/Makefile
create: usr/src/pkgdefs/SUNWsquidu/copyright
create: usr/src/pkgdefs/SUNWsquidu/depend
create: usr/src/pkgdefs/SUNWsquidu/pkginfo.tmpl
create: usr/src/pkgdefs/SUNWsquidu/prototype_com
create: usr/src/pkgdefs/SUNWsquidu/prototype_i386
create: usr/src/pkgdefs/SUNWsquidu/prototype_sparc
Please list all participants in the code review:
Arvind Srinivasan
Jyri J. Virkki
Additional reviewers solicited from
sfwnv-discuss@opensolaris.org and webstack-discuss@opensolaris.org
diffs available for opensolaris.org
http://cr.opensolaris.org/~vrthra/squid/
Y 2.4 Legal review of all licenses completed?
Please provide the number of your review in the legal
review tool
https://opensourcereview.east.sun.com/app
(OSR states as of 4pm 9/21):
Squid #7240 Approved
N Do any licenses pose "Significant Risks"
If so provide details
N 2.5 Have you made any changes to the the open source code?
If so, please provide details of the changes and the
reasons for them
Will your changes be accepted back into the main source
distribution?
If so, when?
If not, why not?
Who is your community contact?
3. Testing
3.1 Describe briefly the testing you have done.
Squid as forward proxy: This involves configuring Squid to
pass HTTP requests directed towards origin servers to the concerned
servers, and passing back the responses to the http client such as a
browser. It also involves setting up ACLs such that some of the requests
are denied and some are allowed and verifying that they work correctly.
Squid as reverse proxy: This involves setting up squid to pass all
requests to a designated HTTP server and passing back the responses
to the requesting client. For the client, the squid server will seem like
the original HTTP server.
Y complete?
10/8 date completed
Y on all supported ISAs?
List supported ISAs: SPARC, x86
3.2 Performance
N Can this project impact Solaris performance?
If so, what benchmarks did you run to show that
there is no performance degradation?
_____CDEbench
_____TPC-C or SO
_____SPECsfs
_____boottime
_____kenbus
_____NetBench
_____SPECweb99
_____SPECjbb
_____other
4. Bugs
N 4.1 Will any bugs against this project remain open at put
Provide a list of all P1 to P5 bugs to remain open:
Are any of these bugs your project has introduced?
__ 4.2 List the existing and/or new cat/subcat to be used for this
project including the RM & IE for each.
New Product/Cat/Subcat RM IE
--- ----------------- -- --
Y solaris/utility/squid Murthy Chintalapati Rahul Nair
Have the snv_xx release values been enabled in bugster? Y
Note: cat/subcat's should follow functional areas, not
organizational lines.
Note also that RMs should be valid names, not aliases.
5. Miscellaneous
____ 5.1 Dependencies
What projects do you depend on?
Do they know about your dependency on them?
What projects depend on you?
Are there any issues regarding their dependency on you?
Squid depends on the below components in solaris.
All these are in nv72 so Squid is not waiting on anything.
SUNWopenssl-libraries : OpenSSL Libraries
SUNWpr : NSPR
SUNWtls : NSS
SUNWkrbu :Kerberos version 5 support
____ 5.2 Documentation work:
Y Will man pages be included in your delivery?
y/n If not, man page request complete or bug filed?
Y Is this a new feature? If yes, complete the
What's New doc template at:
http://releaseme.sfbay/new_features_input.html
y/n 5.3 CTE/Sustaining
_2_ What is the support level for this project?
Note, the default is Level 2, fixes come from the Community.
For details see: http://opensource.uk
____ For Level 1 support only:
Why is Level 1 support necessary for this project?
_N_ Do you have support agreements in place
(List the Group Name and Mgr. Name)
_N_ Have you arranged for a TOI/SRT?
_N_ Have you completed the TPT Feature template at:
http://shwp.eng/TPT/feature-tpttemplate.shtml
6. Packaging
Y 6.1 Any new packages? If so:
List package names:
SUNWsquidr
SUNWsquidu
SUBMITTED, NO ANSWER YET: Pkg RTI submitted to pkgteam@eng and approved?
For instructions see:
http://spgweb.sfbay/SPE/SRE/Process/rti_rtc.html
Y New packages names must also be registered:
http://wolfman.sfbay//SPE/SRE/registry
Which Metacluster(s)?
[X] SUNWCall (Entire distribution)
[X] SUNWCprog (Developer)
[ ] SUNWCuser (End-User)
[ ] SUNWCreq (Core)
[ ] SUNWCrnet (Reduced Networking System Support)
N 6.2 Are there any addtions to the miniroot?
N 6.3 Any changes to existing packages? If so:
List package names to/from which any new objects/headers have
been added/deleted:
Do the changes cause any interpackage dependencies and,
if so, are those packages contained within the same
Metacluster ?
____ 6.4 What is the Footprint/Size Impact?
Package Name Size in Bytes
------------ -------------
SUNWsquidr 295936 bytes
SUNWsquidu 4753408 bytes
N 6.5 Are there any installation or upgrade issues?
N 6.6 Any binaries delivered to /opt or /var?
N 6.7 Any setuid or setgid executables?
7. Integration
Y 7.1 Copyrights
Y Clear statement of ownership as required by open
source licenses for non Sun, open source files.
The SUNWsquidu/install/copyright files contains the text
of the various licenses from the included sources.
N 7.2 Does the software contain encryption?
_____ export-control details provided to C team
(i.e type of encryption, key length, etc)
N 7.3 If your project has a user interface, either command line
or GUI, have you completed the Accessibility Form
(http://solaris.eng/accessibility/assessment/index.html)?
Please provide a pointer to your completed form.
Completed forms are stored in
http://solaris.eng/accessibility/assessment/forms/*
Or provide a date by which it will be completed and
submitted to the Accessibility Program Office.
Y 7.4 Full build of SFW, on all supported ISAs?
(Note: this means running nightly on sparc and x86/64,
with your NIGHTLY_OPTIONS set to "-mpW".)
*TBD* 7.5 Putback -n output and pointer to your workspace
sent to gatekeeper@sfwnv.eng alias?
b77 7.6 What's your current target integration date?
Schedule
CR: 6574325
Sign up or Log in to add a comment or watch this page.