History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: OX-1507
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Monique Szpak
Reporter: Monique Szpak
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
OpenX Ad Server

Upgrade Package Management System

Created: 07/Mar/08 10:48 AM   Updated: 15/May/08 02:15 PM
Component/s: OXP: Developer Tools
Affects Version/s: None
Fix Version/s: Milestone 18
Security Level: Public (All users can see these issues)

Time Tracking:
Original Estimate: 18h
Original Estimate - 18h
Remaining Estimate: 2.92h
Time Spent - 15.08h Remaining Estimate - 2.92h
Time Spent: 15.08h
Time Spent - 15.08h Remaining Estimate - 2.92h

Issue Links:

 Description  « Hide
With many work streams in progress concurrently these days we are coming across the problem of upgrade package clashes and conflicts more and more.

The system of creating a new upgrade package is manual, there is no risk assessment and it relies on developer communications via email and irc.

It was on the wishlist from a year ago that the upgrade system would want some management tools to make the process more efficient and less risky.

It is becoming a higher priority now with the increased number of developers involved in upgrades.

Therefore I would propose that some time is spent on designing (and then implementing) a system for managing the creation, change and deployment of upgrade packages during the development cycle.

Such a system could:
control version numbers
assert correct physical creation of packages
maintain the integrity of packages
assert conflicts
assess risks and create alerts

 All   Comments   Work Log   Change History   FishEye   Crucible   Builds      Sort Order: Ascending order - Click to sort in descending order
Monique Szpak - 15/Apr/08 03:52 PM


integrate svn authentication

User Interface:

schema editor workflow integration
upgrade package inspector
package history inspector
error handling, advisories

Package Management:

offline package inspection
package diffs/integrity checks
unique namespace checks (db objects, tables, columns, indexes)
dbms compatibility checks
declaration checks (default vals etc.)
package registration (not just version no. registration)
namespace registration
mailing list


Extend the process to include Plugin upgrade package management

Monique Szpak - 17/Apr/08 09:21 AM
This work needs further design and implementation phases and has overlap with Developer Tools ticket for Plugins