Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Smooks v1.6
    • Component/s: Release
    • Labels:
      None
    • Number of attachments :
      0

      Description

      See http://sites.google.com/site/smooksdev/release-instructions (need google access).

      Creating the distro:

      1. Update the main POM version number from the project root directory (remove SNAPSHOT suffix).
        mvn versions:set -DnewVersion=newVersionGoesHere
        

        This will create a backup file for every pom.xml in the project with a '.versionBackup' postfix. These can be removed with the following command:

        find . -name 'pom.xml.versionsBackup' | xargs rm 
        
      2. Update the main POM version number from the examples directory (remove SNAPSHOT suffix).
        mvn versions:set -DnewVersion=newVersionGoesHere
        

        This will create a backup file for every pom.xml in the project with a '.versionBackup' postfix. These can be removed with the following command:

        find . -name 'pom.xml.versionsBackup' | xargs rm 
        
        • Delete everything in $USER_HOME/.m2/repository/org/milyn before building. Do this so you can check versions in the local repo before deploying to the central mave repo ("mvn clean deploy -P deploy"). If the pom versions have all been updated properly, you should only see binaries for the version of Smooks you are building. You should not see other versions. If you do see other versions, that means not all the poms have been updated properly, so you need to search a bit. This is very important because we only have one shot at uploading to the release repo (non-SNAPSHOT repo)!!!
      3. Do a dry run of the build ("mvn clean install").
        • Check the versions in the local maven repo. See #1 above.
        • Repeat until versions are all OK in the local repo i.e. you only have binaries for the version of Smooks being released.
      4. Do a release build and deploy of the Smooks binaries ("mvn clean deploy -P deploy").
      5. Run the distro build ("mvn clean package" in smooks-cartridges/smooks-distro).

      Uploads (see release instructions):

      1. Smooks config XSDs
      2. EDI Parser XSDs
      3. Distro and examples to sf.net
      4. javadocs to sf.net

      SVN:

      1. Tag the release

      JIRA:

      1. Finalise the release for that version.

      Wiki Updates:

      1. '''Template:CurrentSmooksVersion''' with release version
      2. '''Template:VX.X_release_tag''' with release tag SVN address
      3. Search and replace "vX.X-SNAPSHOT" in user guide
      4. Downloads page.

        Activity

        Hide
        Tom Fennelly added a comment -

        Don't forget the parser configs too!!

        Show
        Tom Fennelly added a comment - Don't forget the parser configs too!!
        Hide
        Tom Fennelly added a comment -

        Moving to v1.2. We're done with v1.1.

        Show
        Tom Fennelly added a comment - Moving to v1.2. We're done with v1.1.
        Hide
        Tom Fennelly added a comment -

        Moving to the v1.3 release.

        Show
        Tom Fennelly added a comment - Moving to the v1.3 release.
        Hide
        Maurice Zeijen added a comment -

        For the Smooks 1.3 release could you please also upload the http://www.milyn.org/xsd/smooks/persistence-1.2.xsd Schema again? I added documentation to this schema. The schema structure it self didn't change so no new Schema version is required.

        Show
        Maurice Zeijen added a comment - For the Smooks 1.3 release could you please also upload the http://www.milyn.org/xsd/smooks/persistence-1.2.xsd Schema again? I added documentation to this schema. The schema structure it self didn't change so no new Schema version is required.
        Hide
        Tom Fennelly added a comment -

        Moving to v1.5

        Show
        Tom Fennelly added a comment - Moving to v1.5
        Hide
        Tom Fennelly added a comment -

        Moving to v1.6

        Show
        Tom Fennelly added a comment - Moving to v1.6
        Hide
        Daniel Bevenius added a comment -

        Are the following steps required anymore?

        2. Update the version number in assembly.xml
        3. Update the User Guide URL in assembly.xml
        

        I was not able to find an assembly.xml anywhere.

        Show
        Daniel Bevenius added a comment - Are the following steps required anymore? 2. Update the version number in assembly.xml 3. Update the User Guide URL in assembly.xml I was not able to find an assembly.xml anywhere.

          People

          • Assignee:
            Tom Fennelly
            Reporter:
            Tom Fennelly
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: