Diff for "ReleasePolicy" - Free Surfer Wiki

Differences between revisions 4 and 5

Release Policy

This page describes the version release policy for the InternalFreeSurferDistributions. The InternalFreeSurferDistributions consist of 2 versions: FreeSurferStable and FreeSurferDev.

FreeSurferStable
- source /usr/local/freesurfer/nmr-stable52-env
- Stable
- Users are strongly encouraged to use FreeSurferStable, or to keep a copy of it in a project-specific directory like their SUBJECTS_DIR. To make a copy, just download the public distribution from http://surfer.nmr.mgh.harvard.edu/pub/dist/freesurfer
FreeSurferDev
- source /usr/local/freesurfer/nmr-dev-env
- Developmental
- Incorporates the latest features and is updated on a continuous basis.

More details on the two releases are available on InternalFreeSurferDistributions.

-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
-  * {{{source /usr/local/freesurfer/nmr-std-env}}}
+  * {{{source /usr/local/freesurfer/nmr-stable52-env}}}
 Line 9:
-  * Users are strongly encouraged to use FreeSurferStable.

  * Updated for critical bug fixes and when new features which do not affect existing functionality are added.

  * FreeSurferStable is also mirrored as the external distribution which is distributed from http://surfer.nmr.mgh.harvard.edu.
+  * Users are strongly encouraged to use FreeSurferStable, or to keep a copy of it in a project-specific directory like their SUBJECTS_DIR. To make a copy, just download the public distribution from http://surfer.nmr.mgh.harvard.edu/pub/dist/freesurfer
-Line 18:
+Line 16:
- * (Private Distributions) 

  * To obtain a stable, private FreeSurfer distribution you can follow the procedure described under MakingPrivateCopiesOfDistributions. 

  * The FreeSurferSupport team ''will not'' acknowledge technical support requests for private distributions. For a stable, supported distribution users are strongly encouraged to use FreeSurferStable.
-Line 23:
+Line 17:
-The FreeSurfer development team recognizes the critical importance of documenting and communicating changes to the distributions. The development team is working to develop a version control system which is capable of logging changes and describing their effects on standard analysis workflows. If this effort is a top priority for you please add your name next to the Version Control priority on the [[Priorities]] page.