114755 - Create a new despot partition for the NSS_3_3_BRANCH of NSS.

Status: VERIFIED FIXED

(mozilla.org :: Miscellaneous, task)

Description

[Wan-Teh Chang]

We need to have cvs commit access control on the NSS_3_3_BRANCH
of NSS.  Here is the information you need to create this new
partition in despot.

Name: NSS 3.3 Branch
Description: The NSS_3_3_BRANCH of NSS
Newsgroups: netscape.public.mozilla.crypto
Doc links: http://mozilla.org/projects/security/pki/nss/
State: Restricted
Branch: NSS_3_3_BRANCH

files:
mozilla/security/coreconf/*
mozilla/security/nss/*

Owner:
[e-mail]
[e-mail]

Peer:
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]
[e-mail]

Member: none

Comment 1

[Wan-Teh Chang]

Changed the component to "Server Operations".

Comment 2

[Risto Kotalampi]

Moving tickets to Ray.

Comment 3

[Dawn Endico]

This isn't a server issue. removing from ray's queue.

Wan-Teh, could you go over the reasoning behind this again. If I understand
correctly, Mozilla uses the NSS_CLIENT_TAG which is a snapshot in to the
NSS_3_3_BRANCH. Making this partition as you ask means that mozilla will no
longer have access to its own branch and will no longer be able to do things
like change the mac compiler.

Comment 4

[Wan-Teh Chang]

Reasoning behind this request:

Right now there is cvs checkin control on the tip of NSS.
We also need cvs checkin control on the stable release
branches of NSS.  To avoid proliferation of despot partitions,
we only request one despot partition and we will use it to
control checkins to the current NSS stable release branch.

This is the only sure way for us to know whom we need to
notify of NSS code freeze.  We will require everyone who can
check in into the NSS tip and stable release branch to
subscribe to the NSS developers mailing list.  (We announce
code freeze and other important events on the mailing list.)

To address Dawn's concerns, I first want to clarify that
the NSS stable release branch is not used by the Mozilla
client.  The Mozilla client uses NSS_CLIENT_TAG, a tag
provided by the NSS team.  NSS_CLIENT_TAG is usually a
snapshot of the NSS stable release branch, but it does not
need to be.  If the Mozilla client needs an NSS change
urgently and there is a code freeze on the NSS stable
release branch, we can create a "mini" branch off the NSS
stable release branch, check in the change on the "mini"
branch, and produce the NSS_CLIENT_TAG on the "mini" branch.

Last week, the new Mac CW7 project files for NSS were checked
in during the code freeze for the NSS 3.3.2 release. My
investigation found this to be an accident.  Everyone involved
followed the rules -- the changes were reviewed, and a member
(or "peer") of the security team was asked to check in the new
files.  But that person was not on the NSS team mailing list and
was not aware of the code freeze for NSS 3.3.2.  The new despot
partition and the NSS mailing list subscription requirement will
ensure that any conflict in the schedules and code freeze of NSS
and the Mozilla client will be noticed and handled.

If you have any other concerns, please give me a call.  Thank
you for your assistance.

Comment 5

[Dawn Endico]

the partition has been created.

Comment 6

[Wan-Teh Chang]

Thank you, Dawn.