283909 - Retire PSM Product, create Security: UI components

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Darin Fisher]

PSM should have target milestones that correspond to Gecko milestones.

PSM is part of Gecko, so this makes sense.  Moreover, it is helpful to set
target milestones consistently with other Gecko components.

It appears that we have target milestones for mozilla0.9.1 and mozilla0.9.2, but
then the rest of the target milestones are numbers like 2.x.

Comment 1

[Wan-Teh Chang]

I suggest that we deprecate the current PSM *product*
and add a new PSM *component* in the approproate
client product.

Is there a way in Bugzilla to deprecate a product
(i.e., prevent new bugs from being filed against
that product)?

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

hm... can we move PSM/Client Library to Core, renaming it to PSM?

Comment 3

[Asa Dotzler [:asa]]

I like Christian's suggestion. If we move the existing bugs in PSM to a "PSM"
component in Core and then create new "Security UI" components for each of the
apps, then we'd have a more sane system. What do you all think?

Comment 4

[Darin Fisher]

Agreed.  Make it so! :-)

Comment 5

[timeless]

34 bugs left, i can't see them. justdave helped me move 4 netscape confidential
bugs for one of the other components, i need the last 34 moved.

as an interim measure, the product is now closed to prevent people from filing
bugs in it.

Comment 6

[timeless]

for reference:
Product: 	PSM
Description: 	The Personal Security Manager performs all encryption and PKI in
the browser, including SSL, TLS, and certificate management (more info)
Milestone URL: 	http://mozilla.org/projects/security/pki/psm/
Closed for bugs: 	closed
Components: 	
Security: UI:	PSM client library
Versions: 	Other Branch
psm1.01
psm1.1
psm1.2
psm1.3
psm1.4
psm1.5
psm2.0
psm2.1
psm2.2
psm2.3
psm2.4
Edit milestones: 	---
M16
M17
M18
mozilla0.9.1
mozilla0.9.2
psm1.3
psm1.4
psm1.5
psm2.0
psm2.1
psm2.2
psm2.3
psm2.4
Future

Comment 7

[timeless]

the product is now dead. (thanks to asa for evicting the remaining bugs)

if someone provides me with a mapping between the target milestones/versions and
mozilla releases, i'll see about doing a more traditional change once i get that
data (otherwise it'll have to wait for me to do the research which may take a
while).

Comment 8

[Wan-Teh Chang]

On the advanced "Enter Bug" page
(https://bugzilla.mozilla.org/enter_bug.cgi),
we should continue to list PSM but refer people
to its new location in Bugzilla.  We've trained
some people how to file PSM bugs.  They need to
know the new way.  (Right now PSM is still listed,
with no description, and the link merely goes to
an error page.)

Under the Core product, there are "Security: PSM"
and "Security: UI" components.  What's the
difference?

I was hoping that we only migrate the open bugs.
One reason is exactly that we wouldn't need to
map versions and target milestones.  Another
reason is that there is a stand-alone PSM product
that is an add-on to Netscape Communicator 4.x.
That PSM is definitely not part of the Core product.

Comment 9

[timeless]

well, the alternative is that i move the old bugs into derivatives or a
graveyard product, i've wanted to create a graveyard product for a while but
have not spent the time justifying it.

Comment 10

[Wan-Teh Chang]

The migration of old PSM bugs was done poorly.  While
I appreciate voluntary help in general, this was done
without consulting anyone who understands PSM's history
and bugs.  The migration of bugs and mapping to new
product:components was done in a mechanical way and
therefore preserves the problems of the PSM product
in Bugzilla.

The PSM product in Bugzilla has the following problems:
1. It covers two generations of PSM, and these two generations
are essentially different products.
2. Its components (daemon, client library) reflect the
previous generation of PSM and make no sense in the
current generation of PSM.
3. PSM is no longer developed by a separate team and
managed as a separate product.  So the versions and
target milestones no longer reflect how PSM is developed
and managed today.

We've only fixed problem 3, but we failed to fix problems
1 and 2.  We preserved problem 2 because of the mechanical
mapping to new product:components, and we made problem 1
worse because we also migrated the bugs for the previous
generation of PSM (an add-on to Netscape Communicator 4.x).

The Security related components in the Core product in Bugzilla
are:

  Security   	 [e-mail]   	 [e-mail]
  For non-crypto security bugs. Or use this general component
  if you know you have a Browser security bug, but not sure
  what component to use. Bug will be reviewed for proper
  component.

  Security: CAPS [omitted for brevity]

  Security: PSM 	[e-mail] 	
  A daemon that performs cryptographic operations on behalf
  of a client   application.

  Security: S/MIME 	[e-mail] 	
  S/MIME is the sending of signed and/or encrypted email.

  Security: UI 	[e-mail] 	
  PSM client library

With the addition of "Security: PSM" and "Security: UI",
the description of "Security" is a little confusing,
because it now has crypto-related subcomponents.

The "Security: PSM" and "Security: UI" components describe
the previous generation of PSM.  They should be redone to
only reflect the current generation of PSM.  Perhaps
combined into just one component named "Security: PSM"
for lack of a better name.

Comment 11

[timeless]

i'm much more likely to work to kill off the psm component than the ui
component, all the other products have security:ui, and it means more to the non
developers.

as for the migration being done by someone who does not understand the history.
i object. i do understand the history, i've been around long enough to know it.
no one suggested an alternate place for the graveyard bugs (see comment 9), if i
get approval for a graveyard product, i can easily move the psm1.x bugs to it.
as for the old versions and milestones, i need a mapping (see comment 7) and i
don't have one, with a mapping i can make further mass changes. until then,
preserving as much data as possible while killing off the product was the best i
could do. for any new bugs in the security components, please use the standard
milestones. and if you have suggestions for better descriptions, i can take them
here or in another bug.

Comment 12

[Gervase Markham [:gerv]]

Wan-Teh: If further changes to the PSM part of the hierarchy are still required, please comment in mozilla.dev.planning where we are rearranging the hierarchy.

Gerv