Following the 2015 Annual Meeting sponsored by the CTMM/TraIT project and the Netherlands Cancer Institute, the tranSMART Foundation has an updated development roadmap that envisions a new release roughly every 6 months. The roadmap extends through 2017 and targets a commercial-grade, Long Term Support release in 1H2017. The presentation below provides more details on the rationale and timelines of the roadmap.
These pages contain information on the current status of development of tranSMART 16.3.
These pages contain information on the current status of development of tranSMART 16.2.
These pages contain information on the current status of development of tranSMART 17.1.
These pages contain information on the upcoming next release of the tranSMART Foundation Platform. It will contain both the results of the development project tranSMART Pro 17.1 as well as all of the feature of 16.2. The release is expected later in the fall of 2018.
This wiki entry describes the tranSMART Foundation’s release policies for the tranSMART Platform.
Release planning is coordinated through the tranSMART Foundation’s JIRA database. For ideas about what you might contribute to the platform and roadmap, please see the “Project Suggestions” and “How to Contribute” pages.
The official tranSMART Foundation tranSMART releases are numbered in the form of releaseyear.number. That is, for the first release of 2016, the release number is 16.1. The second release for 2016 is 16.2, etc. Releases are planned every 6 months.
The tranSMART platform is on an overlapping six month development / six month release cycle, which will result in a new release every six months. Thus, the Foundation has an active development cycle AND an active release cycle running at all times. For a release, a branch date is selected for the release
tranSMART Release 16.1 (aka v1.2.5) - Release 1st Half of 2016
Release Process Improvements
Digitally signed release materials
PGP signature for official Foundation release
a new, single line install script for Ubuntu/Postgres
bug fixes and general enhancements
bug fixes and general enhancements
updated to work with both Oracle and Postgres
tranSMART v1.2.4 - (released February, 2015)
Added minor improvement: customized spring security messages.
Added security measure: temporarily lock account after some failed login trials (configurable)
Bug fixes: for user groups modification, for cross-trials nodes, for VCF calculations in export
Minor extensions to support (optional) XNAT plugin
Added security measure: user has to enter password for import instead of storing it
Refactor: improved import process and messaging
Fixed RCommandsStep RConnection string encoding
Fixed bug in Survival Analysis (multiple censor variables)
Fixed bug – Clear categorical and numerical bins when clearing high dimensional nodes
Fixed bug in Frequency Plot
Fixed bug: KMeans heatmap-function should not cluster
Fixed bug: Vanilla heatmap should not cluster.
Fixed Bug: Export log-intensity if zscore calculation on the fly is checked
Improvements, UI tweaks, and Refactoring
Added warning note to log10 option in scatter plot
Remove correlation-by selection from gui
Reword error message for ACGH validation
Added validation for high dimensional data nodes and data type
Prune concept to shortest unique leaf
Computation of Z-Score: Categorical variable detection
Added check and error message for missing chromosome/region data
Added validation for numerical variables before binning (heatmap)
Changed legend and scaling for heatmap plots
BoxPlot: Allow multiple variables for binning
Refactor: Made error catching across heatmap analyses consistent
Refactor: Better naming for sort index
Added sorting to tags mapping
Added “two region support”
Added a method to get all concepts by data-type.
Added a method to get all HD nodes for a patient.
Added support for new API methods
Bug fix in composite id
Bug fix for data export
Added test for VFC calculations
Refactoring: whitespace cleanup; clearer function names; better logging
Minor bug fixes in display rendering (UI)
Refactoring: Removed transient fields that are not used.