X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=f3a08d3ae4aa500bbfc044281c16646ae11f53f0;hp=79cf7c98197d9c18e8884964fbeb4c5d7f93cc17;hpb=8a3915baf2a22618346a5a2ecd38f7fbca5d4a44;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 79cf7c9..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,72 +1,78 @@ + --> What's new ? -

- What's new ?
Jalview 2.8.0b1 is a bugfix - release for Jalview version 2.8.
As usual you can find the - highlights below, and the comprehensive list is given in the Jalview 2.8.0b1 Release Notes. -

- This bug fix release includes numerous minor enhancements made over - the last 12 months. Importantly, it is also the first release that - provides Jalview as a trusted application, signed with a certificate - donated to us by Certum. + What's new in Jalview 2.10.1 ? +

+

+ Jalview 2.10.1 was released on 29th November 2016. Full details are + in the Jalview 2.10.1 + Release Notes, but the highlights are below. This is also the + first release to include contributions from Kira Mourão, who + joined Jalview's core development team in October 2016. +

+ + +

+ Warning dialog about updating + your configured URL links
In the desktop prior to Jalview + 2.10.1, the only way to configure custom links for a particular + database cross-reference for a sequence was to give it a name that exactly + matched the database source, and a regular expression for filtering + out any spurious matches generated when the custom linked was tested + against the Sequence's ID string. Since the introduction of the + $DB_ACCESSION$ token, however, $SEQUENCE_ID$ will not be used for + database cross-reference accession strings, and if you have custom + links configured, Jalview will raise a warning message so let you + know that you may need to update your links to use $DB_ACCESSION$.

- Enhancements and new features - - Bug fixes -