Documentation:How to create a Movable Type Change Log

From MovableType

Contents

Overview

This document discusses how a change log for Movable Type is generated.

Steps

  1. Determine the revision number of the branch you want to create a change log BACK to.
  2. Determine the revision number of the branch you want to create a change log UP to
  3. Generate the change log in an XML format
  4. Download or checkout the changelog.pl script from subversion
  5. Convert the change log to markdown using the changelog.pl script
  6. Publish to MovableType.org

Determining a Revision Number

Execute the command against the branch that contains the last revision you are trying to determine. For example:

   svn info http://code.sixapart.com/svn/movabletype/branches/release-35

This will output something like this:

   Path: release-35
   URL: http://code.sixapart.com/svn/movabletype/branches/release-35
   Repository Root: http://code.sixapart.com/svn/movabletype
   Repository UUID: 3860aeb0-bd15-0410-af20-b8d1745f506e
   Revision: 2266
   Node Kind: directory
   Last Changed Author: fumiakiy
   Last Changed Rev: 2042
   Last Changed Date: 2008-04-22 17:20:21 -0700 (Tue, 22 Apr 2008)

You are looking for "Last Changed Rev". That's the number you want.

Generating the Change Log in XML

   svn log --xml -v -r 1895:2019 \
       http://code.sixapart.com/svn/movabletype/branches/release-35 \
       > ~/Desktop/beta3-changelog.xml
  • In the above example 1895 corresponds the number from step 1 above.
  • In the above example 2019 corresponds the number from step 2 above.

Convert the Change Log to Markdown

   perl changelog.pl -log ~/Desktop/beta3-changelog.xml -out ~/Desktop/change_log.txt