Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2006-08-27 16:11:13


We have changed how we generate snapshot tarballs (previously called
"nightly" tarballs). The old way was that if there had been any commits at
all to the SVN repository in the previous 24 hours, we would generate new
tarballs for all active OMPI development trees. For example, if there had
been even a single commit to the SVN trunk in the previous 24 hours,
snapshot tarballs would be created for the trunk, v1.0, v1.1, and v1.2 --
regardless of whether anything had happened on the v1.0, v1.1, or v1.2
branches.

The nightly snapshot tarball generation has now been made smarter in two
ways:

1. Tarballs for particular branches will only be generated if there was a
change *to that branch* since the last time a snapshot was generated.
Hence, snapshots may not be generated every night.

2. The SVN r number of snapshot tarballs will reflect the last commit on
that branch -- not the HEAD when the tarball was made.

For pedantic reasons, we ended up deleting all prior snapshots as of today
and starting with a clean slate (e.g., all the existing v1.0 snapshots were
identical, anyway, because nothing has changed on that branch in a while).
Because some branches change at lower frequency than others, there may only
be one snapshot available for a while. For example, most current work is
focused on the trunk, v1.1, and v1.2 -- there is little work on the v1.0
branch.

I doubt that this will impact anyone, but I did want to explain why you
would potentially only see one snapshot in the v1.0 portion of the web site.

-- 
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems