[kepler-dev] [Bug 4353] New: - Update publishing to allow for patches.

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4353

           Summary: Update publishing to allow for patches.
           Product: Kepler
           Version: 1.x dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: build system
        AssignedTo: welker4kepler at gmail.com
        ReportedBy: welker4kepler at gmail.com
         QAContact: kepler-dev at kepler-project.org
OtherBugsDependingO 4286
             nThis:


It needs to be possible to patch modules deployed in the field. Such patches
should be installed by default (i.e. a prompt should display requesting the
user to allow the patch to be installed). In contrast, major and minor updates
should only occur when requested by the user.

To enable this, appropriate changes need to be made to the build system. Right
now, it does cascading publishing, which is both time intensive and error
prone. Instead, the ability to publish individual modules, where all of the
dependencies of the module are already published, needs to be enabled.

Furthermore, changes to the repository need to be made. Whenever a major or
minor update is contemplated, a new branch must exist. Patches, in contrast,
should occur on an existing branch. Patches never occur on the trunk, but they
can occur from the trunk.