Changes/LegacyJDKsInFedora

draft  draft  draft  draft  draft  draft  draft 

Still under construction

draft  draft  draft  draft  draft  draft  draft 

Legacy JDKs in Fedora

Summary

Currently Fedora supports one main JDK and from time to time one future JDK as techpreview. This change should be set of rules, which will enable community to maintain legacy JDKs

Owner

• Name: Jiri Vanek
• Email: jvanek@redhat.com
  • #fedora-java
  • #fedora-devel
• Release notes owner:
• FESCo shepherd: Would_Be_Nice_To_Have

Current status

• Targeted release: Fedora 22
• Last updated: 2014-02-23
• Tracker bug: <will be assigned by the Wrangler>

Detailed Description

This is no real work proposal. The result of this proposal is set of rules, which will allow community maintainers to pack any legacy jdk and will be ensuring that this JDKs will not conflict by any other JDK. The results are summarized here, and pledged for discussion until final resolution is done.

Benefit to Fedora

There do exists products being developed in Fedora, but targeted for third party. Those products may be targeted for different then Fedora's main JDK. Also there exists out of repo java applications which are bound to older JDK version. To make development of such a product more simple or running of those bounded apps easier, to have legacy JDKs directly in Fedora would be nice

Scope

• Proposal owners: jvanek@redhat.com FESCO (not yet...) omajid@redhat.com dbhole@redhat.com sgehwolf@redhat.com

The FESCO, the owners and pssible legacy JDKs maintainers have to agree on those rules. New legacy JDK can be then added anytime in Fedora lifecycle.

• Other developers: no developers

• Release engineering: in ideal case, no release engineer needed

• Policies and guidelines: The proposal may split to proposal and "Legacy JDKs in Fedora guidelines" pages

Upgrade/compatibility impact

The result of this proposal should ensure, that upgrading users will not be non-volunteerly affected by legacy jdk

How To Test

not interested user

• update of Fedora will not keep legacy jdk on your system, or at least it will not be set as default
• operations with packages will not lead to accidental install of legacy jdk (at least easily)
• you will be able to remove legacy jdk without any complications
• the packages stack will be run by main jdk

interested user

• is able to install legacy jdks without any complications
  • is able to use them (also in parallel with regular one)
  • the packages stack will be run by main jdk (but not obligatory without manual interference)
  • you are able to use the legacy jdk for your work

User Experience

See "How To Test"

Dependencies

• No current package should depend on this proposal
• future legacy JDKS are all depending on the result of proposal
• packages which may depend on legacy jdk may appear in future, but have to attend

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? NO
• Blocks product? NO

Documentation

This proposal itself is an documentation, unless it is split to proposal and guideline.

Release Notes

Release notes should be mentioning, that any legacy jdk which is coming with this Fedora is subject of those conditions.