From Fedora Project Wiki
< Changes
No edit summary |
No edit summary |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
== Summary == | == 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. | 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 == | == Owner == | ||
| Line 32: | Line 32: | ||
== Detailed Description == | == Detailed Description == | ||
Upgrading Horde will provide a much richer webmail and groupware capability to Fedora platforms. | Upgrading Horde will provide a much richer webmail and groupware capability to Fedora platforms. | ||
Examples (but not limited to): | |||
{| class="wikitable" | |||
|- | |||
! 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 | |||
|} | |||
Potential to add meta-packages for horde-groupware and horde-webmail to allow single package install via dependencies. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 38: | Line 81: | ||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the change in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the change in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
This change requires the repackaging of the Horde application stack, rebasing to the latest stable versions. | |||
* Proposal owners: | * Proposal owners: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 52: | Line 95: | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
As far as I understand, the latest version of Horde is compatible with the PHP & PEAR available in Fedora. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 71: | Line 114: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
Horde packages should be capable of being installed and bringing up a base configuration of the various packages. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 87: | Line 132: | ||
== Contingency Plan == | == Contingency Plan == | ||
Do not replace current Horde packages unless testing is passed. | |||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Latest revision as of 14:52, 30 October 2013
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 |
Potential to add meta-packages for horde-groupware and horde-webmail to allow single package install via dependencies.
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)