Changes/HordeUpgrade

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
Line 47: Line 47:
 
| imp
 
| imp
 
| 4.3.10
 
| 4.3.10
| 5.1.5
+
| 6.1.5
 
|-
 
|-
 
| ingo
 
| ingo

Revision as of 14:49, 30 October 2013

Contents

Upgrade Horde Packages

Summary

The Horde application stack has had several large upgrades beyond the versions available in Fedora. Upgrading the Fedora packages will bring a large improvement to the Horde suite available to Fedora users. Extra packages could also be added where Horde has expanded since the last package update.

Owner

  • Name: Duncan Innes
  • Email: duncan@innes.net
  • Release notes owner: <To be assigned by docs team>

Current status

  • Targeted release: Fedora 21
  • Last updated: 2013-10-30
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Upgrading Horde will provide a much richer webmail and groupware capability to Fedora platforms.

Examples (but not limited to):

Package RPM Version Horde Release
horde 3.3.13 5.1.5
imp 4.3.10 6.1.5
ingo 1.2.5 3.1.3
gollem 3.0.1
kronolith 2.3.5 4.1.4
mnemo 4.1.2
nag 4.1.3
turba 2.3.5 4.1.3


Benefit to Fedora

Keeps Fedora up to date with one of the larger web based groupware application stacks.

Scope

This change requires the repackaging of the Horde application stack, rebasing to the latest stable versions.

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

As far as I understand, the latest version of Horde is compatible with the PHP & PEAR available in Fedora.

N/A (not a System Wide Change)

How To Test

Horde packages should be capable of being installed and bringing up a base configuration of the various packages.

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

Do not replace current Horde packages unless testing is passed.

  • 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

Documentation

N/A (not a System Wide Change)

Release Notes