X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=47fd498a6fe7d2e3350a9e87c526bf1e59d00be5;hp=f8de1f0b610ee1076612e8109a404c5c3ee97c15;hpb=21c2deb35c435e6097b0f05c83d21cfdf4929ba2;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index f8de1f0..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -24,61 +24,55 @@

- What's new in Jalview 2.10 ? + What's new in Jalview 2.10.1 ?

- Jalview 2.10 is the next major release in the Jalview 2 series. Full - details are in the Jalview - 2.10 Release Notes, but the highlights are below. + 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$. +