From Fedora Project Wiki

< Changes

Revision as of 23:43, 26 December 2013 by Boblfoot (talk | contribs) (F21 release planning update package change to alpha sorting folders)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Change Proposal Name <AlphabeticalSortedUpdatesPackages>

Summary

<Present Releases have sorted packages released by first letter {a-z}{0-9} folders; but update packages remain in one huge mess folder. This proposal requests that the same logic be applied to updates as was applied to base packages.>

Owner

  • Name: Bob Lightfoot
  • Email: <boblfoot AT fedoraproject DOT org>
  • Release notes owner:

Current status

  • Targeted release: [[Releases/<21> | Fedora 21 ]]
  • Last updated: (2013-12-26)
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

< Looking at ​http://dl.fedoraproject.org/pub/fedora/linux/releases/19/Fedora/i386/os/Packages/ shows that they are sorted by First Letter a-z ; 0-9 and yet looking at ​http://dl.fedoraproject.org/pub/fedora/linux/updates/19/i386/ shows one large pile of packages with no sorting. This request is to beginning with F21 start sorting the packages in updates like we do in releases >

Benefit to Fedora

<In most cases not all update pacakges will need to be parsed when searching for packages. Having a sorted tree will improve response over having to load the index of the larger current folder.>

Scope

<The work and methods applied when base packages were sorted will need to be replicated here.>

  • Proposal owners:

<Proposal owner will do housekeeping and oversight work as assigned by Wrangler and FESCO>

  • Other developers: System Wide Change

<YUM and all package handling mechanism will need to accommodate the new tree sorted folder approach for updates as is done for base packages.>

  • Release engineering: System Wide Change

This is a proposal to change update package delivery format? No rel-eng ticket exists yet , will add a link here when one does. -->

  • Policies and guidelines: System Wide Change
 The packaging guidelines or other documents will need to be updated for this feature?  If so, owner is unsure when it needs to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

0. No Special hardware, data or etc. is needed. 1. This change will need an F21 System installed/ 2. Application of any update from updates or updates-testing would constitute a test of this proposal if the updates and updates-testing repos are in the new sorted tree format. 3. The Sorted Tree Updates should behave like previous unsorted.? -->

User Experience

User experience should notice faster updates as the entire package lsit will not need to be passed/read over the update connection.

Dependencies

Not sure what is dependent on this. Wrangler Input??

Contingency Plan

  • Contingency Plan: Revert to the Previous Unsorted Tree Method
  • Contingency mechanism: Fedora Rel Eng will chose when to trigger the Contingency Plan
  • Contingency deadline: Beta Freeze Deadline
  • Blocks release? This feature or the fallback must be in place.

Documentation

https://fedorahosted.org/bodhi/ticket/744

Release Notes