Creating a manual release by attaching a file

A manual release is a .zip file containing the files needed to use a project. This usually means one or more Igor Pro procedure files (.ipf) but may also include compiled code in the form of external operations (XOPs), source code, and/or Igor Pro experiment files.

Releases can be created either by attaching a file to a release node or creating a release node based on a Subversion branch or tag and letting the packaging scripts on the server automatically package the release into a file that can be downloaded. Only a project's owner or a maintainer of a project can create a release for that project. This help topic covers the manual method of creating a release. If you need help with the Subversion method, please see Creating a release with Subversion.

There are two types of releases, official releases and development snapshots, but development snapshots are used only with projects that use Subversion for version control.

Follow these steps to create a new manual release:

  1. You first need to create a release node for the release. You do this by clicking the "Add new release" link on the project summary page.
  2. In the Categories section, select the version of Igor Pro that can be used with your project (if more than one version of Igor Pro will work, choose the earliest version). Also, select one or more operating systems that are supported by the release you are creating. Most procedure files will work on any operating system; XOPs must be specifically compiled for each operating system. Use Ctrl-click (Windows) or Cmd-click (Macintosh) to select multiple operating systems.
    Project Release CategoriesProject Release Categories

  3. Fill out the version number elements to indicate the version of the project for the release you are creating.
  4. Click the Browse button to upload the file for the release.
  5. In the body field, describe the major changes present in this release compared to previous releases. Be as descriptive here as possible, so that your users know the advantages (or disadvantages) of your new release.
  6. When you finish filling out all of the fields, click the Submit button. If you filled in all fields appropriately, you will get a message telling you that your release node was created.

Back to top