These are the release notes for Swift 0.7

More information about Swift can be found at http://www.ci.uchicago.edu/swift/

Swift 0.7 is built from Swift SVN r2318 and cog SVN r2255.

The following are significant changes since Swift 0.6 was released.

Language changes:
*  readData2 procedure allows reading of data from a file in a format similar
   to that used by the external mapper. This can sometimes be easier and more
   expressive than using the plain readData format. See:
   http://www.ci.uchicago.edu/swift/guides/userguide/procedures.php#procedure.readdata2
*  Empty statements are no longer allowed in SwiftScript programs.
*  A simpler syntax has been introduced for application procedures. The
   previous syntax will continue to work for a number of future releases.
   The new syntax is shown here:
   http://www.ci.uchicago.edu/swift/guides/userguide/language.php#procedures.atomic

Coasters:
*  Coasters can now transfer files. This can be used when there are a
   large number of small files to transfer during a run. See:
   http://www.ci.uchicago.edu/swift/guides/userguide/coasters.php
*  A large amount of testing and bugfixing on the coaster code should make
   runs with coasters substantially more reliable.

Configuration changes:
*  Swift will find executables on the remote system $PATH if no explicit
   path is specified for an application executable in tc.data
*  Configuration files in the ~/.vdl2 directory are now ignored. Previously,
   attempting to use a ~/.vdl2 configuration file would give an error message.

Replication:
*  The expected queue time for the first job executed is now guestimated for
   replication purposes, so that job can be replicated if necessary.
   Previously, the first job would never be replicated as there was
   insufficient information to estimate its expected queue time.

Minor bugfixes:
*  Uninitialised state was missing from list of known states in runtime
   ticker, causing it to appear at the end of status list rather than
   its more natural position at the start.
*  The stageout destination directory is created using the same destination
   host and provider as the actual stageout transfer. Previously, the
   stageout directory was always created locally, which was incorrect
   when using remote stageout URLs.
*  Better walltime handling to work with more LRM backends in GRAM

Packaging:
*  Swift is now available in VDT-friendly pacman form to facilitate use
   alongside the OSG software stack.