Opened 13 years ago

Closed 12 years ago

#256 closed task (fixed)

Filenames and Version strings

Reported by: ajj Owned by: srkline
Priority: major Milestone: General Package Release Tasks
Component: Analysis Keywords:
Cc: Blocking:


Make sure that all filenames and version strings represent our chosen release number.

Since we are now doing a whole package, should we move to a common versioning for all packages?

e.g. should we call this release 6.0 for everything?

Change History (3)

comment:1 Changed 13 years ago by ajj

  • Milestone set to General Package Release Tasks

comment:2 Changed 12 years ago by srkline

the version numbers "SANS_ANA_VERSION" that are in the initialization routines of each package aren't used for anything. "SANS_ANA_EXTENSION" is used to determine what ipf files to load, and this shouldn't be changed from the "v40"

PACKAGE_VERSION is used to determine the overall package version, and is only read from the .txt files. The other versions in the .txt files are rather meaningless.

currently, we're at 6.011 on the web site.

comment:3 Changed 12 years ago by srkline

  • Resolution set to fixed
  • Status changed from new to closed

Package is now 7.00, and we'll work up from there. Old version numbers are still on the separate components, but the 7.++ will track with any changes.

Note: See TracTickets for help on using tickets.