Closed Bug 7178 Opened 26 years ago Closed 24 years ago

Doc ability to drop new version of Netscape into existing CCK

Categories

(CCK Graveyard :: CCK-Wizard, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: bijals, Assigned: kristif)

Details

The ability to drop new version of Communicator into CCK 5.0 should be documented in the CCK Administrator's guide.
Assignee: selmer → robinf
Another docs reminder from Bij...
Assignee: robinf → ornduff
Reassigning to Tina. She's planning to document this in the chapter on deployment, under the topic "Upgrading from 5.0 to 5.x versions of Communicator."
guestimating tfv, please verify
Status: NEW → ASSIGNED
I will add this information to the Admin Guide.
Target Milestone: M12 → M13
changes target milestone to M13.
Target Milestone: M13 → M17
changed target milestone to M17 to reflect new schedule
This bug was vandalized by a clueless idiot. I believe I have undone all of the vandalism.
changing target milestone to M18.
Target Milestone: M17 → M18
reassigning to Steve Rudman
Assignee: ornduff → rudman
Status: ASSIGNED → NEW
Accepting until we can find a replacement writer. Setting target to M20.
Status: NEW → ASSIGNED
M18 to M20
Target Milestone: M18 → M20
Marking as Future
Target Milestone: M20 → Future
changing QA contact to blee
QA Contact: bmartin → blee
Not sure that I understand this bug description, but because this is old bug that refers to a non-existent product (CCK 5.0,) and because we didn't provide tools for migrating Communicator customizations to Netscape6, I'm resolving this as WONTFIX. If I missed the point here and this bug should be handled differently, please let me know.
Group: netscapeconfidential?
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Communicator will NOT work with the new CCK... so if this is still a bug it needs to be reworded. Communicator 4.x will only work with CCK 4.x. N6+ can be "dropped" into the new 6x CCK so I think you can mark this bug as invalid.
Reopening bug. Revising summary. The issue is whether Netscape 6.01 bits, for example, can be dropped into Netscape 6 CCK so that one can produce a customized build of NS 6.01...and I think the REAL issue is whether we document that fact (so I added the "doc" reference in the summary).
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: Ability to drop new version of Communicator into existing CCK → Doc ability to drop new version of Netscape into existing CCK
Reassigning to Kristi. Could you please check with Robin whether she doc'd this? If not, we should reset this bug to cover the 6.5 docs.
Assignee: rudman → kristif
Status: REOPENED → NEW
Is this still a useful report? If it is can someone please remove the Netscape Confidential flag or if there is real proprietary info I'll be glad to file a clean version so we can resolve this Netscape Confidential bug as invalid.
Status: NEW → ASSIGNED
a clean version of this bug needs to be filed if it is going to remain open.
Marking as Fixed. Release Notes for CCK and BDP website both indicate which versions of CCK are compatible with which version of Netscape.
Group: netscapeconfidential?
Status: ASSIGNED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Marking verified per kristif's comment.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.