X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=4dfc54e201bb54ba3074ac62ae61e29135f9e099;hb=0e575263043797b2e9bbd74386cd5851c09433af;hp=1c2088579ed5e6c1ff6426efcdcc65b30092e996;hpb=7585bdc21653bdb66d604ed5efa95497f28c7eb5;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 1c20885..4dfc54e 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -24,55 +24,34 @@

- What's new in Jalview 2.10.1 ? -

-

- Jalview 2.10.1 was released on 24th 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. + What's new in Jalview 2.10.5 ?

+

Jalview 2.10.5 is a minor release that includes critical + patches for users working with Ensembl, and RNA secondary structure + annotation.

-

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

+ The full list of bugs fixed in this release can be found in the 2.10.5 Release Notes. The majority of improvement in 2.10.5 are due to Jalview users + contacting us via the jalview-discuss email list. Thanks to everyone + who took the time to do this !

+

Jalview and Java 10

+

This release addresses a critical bug for OSX users who are + running Jalview with Java 10 which can prevent files being saved + correctly through the 'Save As' dialog box. The 'Save As' dialog for + Jalview's Groovy Console remains affected - we hope to address this + in the next major release.