Revision as of 22:00, 1 March 2019

Changes/Remove389Console

Summary

Remove all the deprecated 389-console packages: 389-console, 389-ds-console, 389-admin-console, 389-dsgw, 389-admin, and 389-adminutil. These packages are for the old JAVA UI for 389 Directory Server. We have a new web UI that is replacing these java packages.

Owner

Name: Mark Reynolds
Email: mreynolds@redhat.com
Release notes owner:

Current status

Targeted release: Fedora 31
Last updated: 2019-03-01
Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The java packages have alreayd been deprecated, and we'd like toremove them in F31(rawhide)

Benefit to Fedora

Cleaning out old deprecated packages

Scope

Proposal owners:

Other developers: N/A (not a System Wide Change)

Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)

Policies and guidelines: N/A (not a System Wide Change)

Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

There are no manual changes that need to be done once this product is removed.

How To Test

The package should no longer be available

User Experience

Users will no longer be able to use the old java UI, and they must now use the new cockpit UI plugin for managing the directory server.

Dependencies

There are no dependencies as we are trygin to remove the entire standalone product

Contingency Plan

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? N/A (not a System Wide Change), Yes/No
Blocks product? product

Documentation

It has been announced upstream via maling lists tahtthe 389-consoel [package suite was being replaced by a cockpiut plugin. But there was no other type of announcement done yet.

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
-<!-- Self Contained or System Wide Change Proposal?
-Use this guide to determine to which category your proposed change belongs to.
-Self Contained Changes are:
-* changes to isolated/leaf package without the impact on other packages/rest of the distribution
-* limited scope changes without the impact on other packages/rest of the distribution
-* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
-System Wide Changes are:
-* changes that does not fit Self Contained Changes category touching
-* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
-* changing system defaults
-For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
-improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).
-We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
--->
 <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
@@ Line 127: / Line 107: @@
 -->
-[[Category:ChangeReadyForWrangler]]
+[[Category:ChangeAnnounced]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Search

Changes/Remove389Console: Difference between revisions