MapGuide RFC 111 - Deploy Viewer Code with Subversion Attributes

This page contains a change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.

Status

RFC Template Version	(1.0)
Submission Date	(Date / Time submitted)
Last Modified	(your name here) (modification date here)
Author	(Zac Spitzer)
RFC Status	(draft)
Implementation Status	(pending)
Proposed Milestone	(2.2.1)
Assigned PSC guide(s)	(when determined)
Voting History	(vote date)

Overview

Change the deployment options for MapGuide so that the viewers, AJAX and Fusion are deployed with subversion attributes, to allow updates without requiring a full build

Motivation

Creating new builds for all platforms is a lot of work. This approach avoids the requirement to generate builds only to deploy a few text file changes which are stored as-is in subversion.

It's low impact for production environments to svn update a few directories, compared to un-installing and re-installing the entire application.

Hacking the viewer code becomes much easier for users. Being able to diff and revert any changes, encourages users to experiment and then hopefully generate and submit patches for bug fixes and enhancements.

Proposed Solution

Update installer build to include subversion attributes

Check in a compiled version of fusion into the mapguide svn repo

Implications

The build process for MapGuide will need to be modified to allow a built version for fusion to be checked into subversion (branches & trunk)

Bug fixes and updates for the viewers can be deployed quickly, reducing the need for full builds to be created only to update a few text files

Test Plan

N/A beyond existing test procedures for builds

Funding / Resources

Ennoble Consultancy Australia