Software Release Policies - Revision history

Maechlin at 03:03, 4 February 2011

2011-02-04T03:03:19Z

Maechlin at 03:01, 4 February 2011

2011-02-04T03:01:19Z

Maechlin at 03:00, 4 February 2011

2011-02-04T03:00:59Z

Maechlin at 03:00, 4 February 2011

2011-02-04T03:00:35Z

Maechlin at 02:58, 4 February 2011

2011-02-04T02:58:23Z

Maechlin at 02:57, 4 February 2011

2011-02-04T02:57:34Z

Maechlin at 17:19, 2 September 2010

2010-09-02T17:19:23Z

Maechlin at 16:09, 1 September 2010

2010-09-01T16:09:23Z

Maechlin: Created page with ' SCEC software engineering group has established standard practices for use when releasing new versions of publicly distributed scientific software. These practices are based on …'

2010-08-16T17:22:14Z

Created page with ' SCEC software engineering group has established standard practices for use when releasing new versions of publicly distributed scientific software. These practices are based on …'

New page

SCEC software engineering group has established standard practices for use when releasing new versions of publicly distributed scientific software. These practices are based on "best practices" for scientific software development established on SCEC's CSEP project and on SCEC's UseIT SCEC-VDO project.

Every SCEC/CME project that releases SCEC-developed and SCEC-supported software to the community is expected to provide the following materials before the software is released, unless there is a good reason not to follow these guidelines. Before the SCEC/CME software development group distributes a new version of software, every software project must have the following items:

# A public SCECpedia entry that provides and overview of the software project, the capabilities of the software, and a software release history.
# A private SCECpedia entry that describes the software development information for the project including design overview, data sources, algorithms used, software language, development environment, run-time environment, and required software stack.
# Copyright statement included in source code.
# Source code under version control.
# Automated make capability such as makefile or ant script.
# Issue tracking system (TRAC) site with a trouble ticket system and a connection to source code under version control.
# Automated suite of unit tests designed to verify the software was installed correctly and is functional.
# Automated suite of user-oriented acceptance tests typically-based on reference inputs and outputs compared to calculated results.
# Automated build and test capability, such as CruiseControl, which will run the acceptance tests without manual interactions.
# Release Version assigned using CSEP model of Yr.Mo.x (e.g. v10.8.0) with tags in version control system.
# Release Notes, as wiki and pdf, containing the following information:
##Software name (or system name) and description of purpose of software
##Link to public web page describing project
##Description of software capabilities
##Description of intended users
##Limitations or known bugs
##Version of current release
##Overview of changes including new capabilities of current release
##Software support email list
##Contact for Responsible scientists
##Contact for Responsible Software Engineer
##How to report software problem or request features
# User documentation, as wiki and pdf, including:
## Computer User Guide to installing, building, verifying, and operating software
## Scientific User Guide to using software, running reference problem, and interpreting results

@@ Line 10: / Line 10: @@
 # Issue tracking system (such as TRAC) site with a trouble ticket system and a connection to source code under version control.
 # Automated suite of unit tests designed to verify the software was compiled correctly and is functional.
-# Automated suite of user-oriented acceptance tests typically-based on reference inputs and outputs compared to calculated results.
+# Automated suite of user-oriented acceptance tests typically-based on reference inputs and outputs compared to calculated results to show the software is installed correct and is operating in the users computer environment the way it operated in the development environment.
-# Automated build and test capability, such as Cruise Control, which will run the acceptance tests without manual interactions.
+# Automated build and test capability (such as Cruise Control) which will run the acceptance tests without manual interactions.
 # Release Version assigned using CSEP version format of Yr.Mo.x (e.g. v10.8.0 as Year.Month.RevisionNumber) with tags in version control system.
 # A persistent, dated, and maintained, web-based Software Project home page that provides, at a minimum, an overview of the software project, links to software download, and the current release version.

@@ Line 8: / Line 8: @@
 # Source code under version control.
 # Automated make capability using standard software distribution tools such as configure, make file, and ant scripts.
-# Issue tracking system (TRAC) site with a trouble ticket system and a connection to source code under version control.
+# Issue tracking system (such as TRAC) site with a trouble ticket system and a connection to source code under version control.
 # Automated suite of unit tests designed to verify the software was compiled correctly and is functional.
 # Automated suite of user-oriented acceptance tests typically-based on reference inputs and outputs compared to calculated results.

@@ Line 7: / Line 7: @@
 # Copyright statement included in distribution.
 # Source code under version control.
-# Automated make capability using accepted software distribution tools such as configure, make file, and ant scripts.
+# Automated make capability using standard software distribution tools such as configure, make file, and ant scripts.
 # Issue tracking system (TRAC) site with a trouble ticket system and a connection to source code under version control.
 # Automated suite of unit tests designed to verify the software was compiled correctly and is functional.

@@ Line 12: / Line 12: @@
 # Automated suite of user-oriented acceptance tests typically-based on reference inputs and outputs compared to calculated results.
 # Automated build and test capability, such as Cruise Control, which will run the acceptance tests without manual interactions.
-# Release Version assigned using CSEP version format of Yr.Mo.x (e.g. v10.8.0) with tags in version control system.
+# Release Version assigned using CSEP version format of Yr.Mo.x (e.g. v10.8.0 as Year.Month.RevisionNumber) with tags in version control system.
 # A persistent, dated, and maintained, web-based Software Project home page that provides, at a minimum, an overview of the software project, links to software download, and the current release version.
 # Capability to track software downloads including at a minimum number of downloads

@@ Line 3: / Line 3: @@
 Every SCEC/CME project that releases SCEC-developed and SCEC-supported software to the community is expected to provide the following materials before the software is released, unless there is a good reason not to follow these guidelines. Before the SCEC/CME software development group distributes a new version of software, every software project must have the following items:
-# A public SCECpedia entry that provides and overview of the software project, the capabilities of the software, and a software release history.
+# A public SCECpedia entry that provides an overview of the software project, the capabilities of the software, and a software release history.
 # A private SCECpedia entry that describes the software development information for the project including design overview, data sources, algorithms used, software language, development environment, run-time environment, and required software stack.
 # Copyright statement included in source code.

@@ Line 11: / Line 11: @@
 # Automated suite of unit tests designed to verify the software was installed correctly and is functional.
 # Automated suite of user-oriented acceptance tests typically-based on reference inputs and outputs compared to calculated results.
-# Automated build and test capability, such as CruiseControl, which will run the acceptance tests without manual interactions.
+# Automated build and test capability, such as Cruise Control, which will run the acceptance tests without manual interactions.
-# Release Version assigned using CSEP model of Yr.Mo.x (e.g. v10.8.0) with tags in version control system.
+# Release Version assigned using CSEP version format of Yr.Mo.x (e.g. v10.8.0) with tags in version control system.
 # A persistent, dated, and maintained, web-based Software Project home page that provides, at a minimum, an overview of the software project, links to software download, and the current release version.
 # Release Notes, as wiki and pdf, containing the following information:
 ##Software name (or system name) and description of purpose of software