X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=7dfc6aec87248b15f6a01c5eb1584f39f21d4233;hp=d7a93c663053851d95c262190701a55b69229d6d;hpb=68ba1a55efa08e12e4381bb0e5bdcb70318e1dd5;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index d7a93c6..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -24,16 +24,55 @@
- What's new ? + What's new in Jalview 2.10.1 ?
- Jalview 2.9.1 is the next major release in the Jalview 2.9 series. Full details are in the - Jalview 2.9.1 Release Notes. + 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.
-- Highlights in Jalview 2.9.1
+ 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$.
+