Skip to content
Snippets Groups Projects
Commit 267eea64 authored by Vermaat's avatar Vermaat
Browse files

Merge pull request #152 from mutalyzer/release-2.0.16

Release 2.0.16
parents 65e685bf d64398bf
No related branches found
No related tags found
No related merge requests found
......@@ -4,12 +4,46 @@ Changelog
This is a record of changes made between each Mutalyzer release.
Version 2.0.16
Version 2.0.17
--------------
Release date to be decided.
Version 2.0.16
--------------
Released on February 25th 2016.
- Fixed transcript naming in mapping webservices (`#147
<https://github.com/mutalyzer/mutalyzer/pull/147>`_). See below for
:ref:`details <changelog_2016_details>`.
- Support LRG transcripts in the position converter (`#147
<https://github.com/mutalyzer/mutalyzer/pull/147>`_).
- Don't report ``ext*?`` when variant RNA has stop codon (`#146
<https://github.com/mutalyzer/mutalyzer/pull/146>`_).
.. _changelog_2016_details:
The following three webservice methods return a list of transcript identifiers
for some query:
- `getTranscriptsRange`
- `getTranscripts`
- `getTranscriptsByGeneName`
Previously they didn't work correctly for LRG transcripts (a bogus version was
included and no transcript was selected) and RefSeq transcripts on mtDNA (no
transcript was selected).
Additionally, the `getTranscriptsMapping` webservice method didn't return
enough information to construct a complete transcript name. This is now
reported in a new `transcript` field.
Finally, the `getTranscriptsRange` method now optionally includes version
numbers with the boolean `versions` argument (default `false`).
Version 2.0.15
--------------
......
......@@ -21,8 +21,8 @@ from __future__ import unicode_literals
# [1] http://peak.telecommunity.com/DevCenter/setuptools#specifying-your-project-s-version
# [2] http://semver.org/
__version_info__ = ('2', '0', '16', 'dev')
__date__ = '6 Jan 2016'
__version_info__ = ('2', '0', '17', 'dev')
__date__ = '25 Feb 2016'
__version__ = '.'.join(__version_info__)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment