X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;fp=help%2Fhtml%2FwhatsNew.html;h=c5859eacb61600f8cbd52cec6104b7bf071affd5;hb=09b25d3dc80f74c0fae97e27fd394417917f3906;hp=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hpb=d8bf5506216e7a0726a1fa5baa6b4d244f035741;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index d1d141d..c5859ea 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -24,55 +24,13 @@

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

- 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. -

+ Full details about Jalview 2.10.2 are in the + Release Notes, but the highlights are below.

-

- 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$. -