Changes between Initial Version and Version 1 of MapGuideRfc111


Ignore:
Timestamp:
Mar 19, 2011, 8:18:12 AM (13 years ago)
Author:
zspitzer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc111

    v1 v1  
     1= !MapGuide RFC 111 - Deploy Viewer Code with Subversion Attributes =
     2
     3This page contains a change request (RFC) for the !MapGuide Open Source project.
     4More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     5
     6
     7== Status ==
     8
     9||RFC Template Version||(1.0)||
     10||Submission Date||(Date / Time submitted)||
     11||Last Modified||(your name here) (modification date here)||
     12||Author||(Zac Spitzer)||
     13||RFC Status||(draft)||
     14||Implementation Status||(pending)||
     15||Proposed Milestone||(2.2.1)||
     16||Assigned PSC guide(s)||(when determined)||
     17||'''Voting History'''||(vote date)||
     18
     19== Overview ==
     20
     21Change the deployment options for MapGuide so that the viewers, AJAX and Fusion
     22are deployed with subversion attributes, to allow updates without requiring a full build
     23
     24== Motivation ==
     25
     26Creating new builds for all platforms is a lot of work. This approach avoids the
     27requirement to generate builds  only to deploy a few text file changes which
     28are stored as-is in subversion.
     29
     30It's low impact for production environments to svn update a few directories,
     31compared to un-installing and re-installing the entire application.
     32
     33Hacking the viewer code becomes much easier for users. Being able to diff and revert
     34any changes, encourages users to experiment and then hopefully generate and submit 
     35patches for bug fixes and enhancements.
     36
     37== Proposed Solution ==
     38
     39Update installer build to include subversion attributes
     40
     41Check in a compiled version of fusion into the mapguide svn repo
     42
     43== Implications ==
     44
     45The build process for MapGuide will need to be modified to allow a built version
     46for fusion to be checked into subversion (branches & trunk)
     47
     48Bug fixes and updates for the viewers can be deployed quickly, reducing the need for
     49full builds to be created only to update a few text files
     50
     51== Test Plan ==
     52
     53N/A beyond existing test procedures for builds
     54
     55== Funding / Resources ==
     56
     57Ennoble Consultancy Australia