From Fedora Project Wiki
(Initial revision)
 
m (Add releng ticket number)
Line 50: Line 50:
* Other developers: N/A (not a System Wide Change)
* Other developers: N/A (not a System Wide Change)


* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Release engineering: [https://pagure.io/releng/issue/7989 #7989]
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change)
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change)


Revision as of 13:31, 12 December 2018

Deprecate Apache Jakarta ORO and Regexp

Summary

Mark Apache Jakarta ORO and Apache Jakarta Commons Regexp software packages as deprecated.

Owner

Current status

  • Targeted release: Fedora 30
  • Last updated: 2018-12-12
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Apache Jakarta has been retired in year 2011 [1]. ORO and Regexp subprojects were both retired even earlier and no new features or releases are planned in the future [2] [3]. Users can migrate to similar regular expression features provided in current Java versions.

Apache Jakarta ORO and Apache Jakarta Commons Regexp software packages are intended to be eventually removed from Fedora, but are kept in Fedora for some additional, indeterminate time for various reasons including maintaining backwards compatibility. In order to prevent new packages from depending on these packages, they are marked as deprecated.

As of time of submision of this change proposal, 29 Fedora components stil Require or BuildRequire Apache Jakarta ORO and Apache Jakarta Commons Regexp packages, therefore immediate retirement of these packages is not feasible at this point.

Benefit to Fedora

Packages of obsolete Apache Jakarta ORO and Apache Jakarta Commons Regexp software will be clearly and explicitly marked as deprecated. Other packages in Fedora will not be able to add dependencies on deprecated packages (that includes Requires, BuildRequires, Recommends, Suggests, etc.). This applies both for updates of existing packages and new packages added to Fedora. This in turn will make it easier to gradually remove dependencies on deprecated packages and finally remove deprecated Apache Jakarta software from Fedora.

Scope

  • Proposal owners: add special virtual provides deprecated() to all packages built from jakarta-oro and regexp source components.
  • Other developers: 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

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

No change in user experience. Technically, nothing changes; deprecated packages work and behave as before.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: 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)

Documentation

N/A (not a System Wide Change)

Release Notes

  1. ↑ https://jakarta.apache.org/
  2. ↑ https://jakarta.apache.org/oro/
  3. ↑ https://jakarta.apache.org/regexp/
Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Deprecate_Apache_Jakarta_ORO_and_Regexp&oldid=530435"