SequenceServer - 1.1.0-beta "testing" release with improved architecture & features

Dear all,

We are pleased to announce a “beta” release of the next major version of SequenceServer - 1.1.0-beta for testing.

We have fundamentally restructured how SequenceServer works in order to achieve two goals.

  1. Most importantly, with the approach used to date, we were limited in what we could do with visualisations and filtering. The new approach overcomes all of this.
  2. We felt it was important to be able to bookmark and share BLAST results, and be able to return to them at a later date.

This new version incorporates multiple new minor features (full list below for details), but the biggest change is the “under the hood” restructuring. Today’s beta release is experimental - it has some limitations we know about, and we hope that you can help us find those that remain unknown. We expect this release to be the first of a series of small regular improvements each incorporating additional new features.

While we have begun using this version for real things, we consider it a “development” rather than a “production” release. Please use with care and report any problems on the github tracker or on this thread.

Features

Hello,

We are pleased to announce 2nd beta release of SequenceServer 1.1.0 for testing.

Changelog

Hello,

We are pleased to announce 3rd beta release of SequenceServer 1.1.0 for testing.

Changelog

Hello,

We are pleased to announce 4th beta release of SequenceServer 1.1.0 for testing.

Changelog

Hello,

We are pleased to announce 5th beta release of SequenceServer 1.1.0. This
release activates the circos visualisation for testing and fixes a few
other bugs. Detailed changelog and a rough roadmap to stable release
below.

Changelog

Hello,

We are pleased to announce 6th beta release of SequenceServer 1.1.0
for testing. In this release we have enabled one more visualisation,
focused on optimising the results page, and fixed some bugs.

Changelog

Hello,

We are pleased to announce 7th beta release of SequenceServer 1.1.0. In this
release we have addressed inconsistencies created by asynchronous rendering
of results that was introduced in previous release, made a few enhancements
and bug fixes, and introduced one final visualisation.

Changelog

Hello,

We are pleased to announce 8th beta release of SequenceServer 1.1.0. This
is a small release that fixes an issue introduced by the previous release.

Changelog

Hello,

We are pleased to announce 10th beta release of SequenceServer 1.1.0. Based on
popular demand we added a button to select all databases. We have further made
several visual and speed improvements to the results page and fixed an
important bug.

Features

Hello,

We are pleased to announce 11th beta release of SequenceServer 1.1.0. This
release includes many small-small bug fixes and enhancements.

Changelog

Hello,

We are pleased to announce 12th beta release of SequenceServer 1.1.0. This
release includes a few small enhancements and several code-style improvements.

Changelog

Dear all,

We are pleased to announce the last beta release of this series. In this release,
we have added a few features based on popular demand and fixed tons of bugs.

You can find a detailed list of changes on our GitHub release page:
https://github.com/wurmlab/sequenceserver/releases/tag/2.0.0.beta4.

Overall, the new architecture now feels quite robust and has seen a growing
adoption within the community. We have incremented the version number to 2.0 to
reflect this milestone. We thank you for your patience, encouragement, and support.

We invite you to try it out and help us get to stable version by sending us a
pull-request or reporting any bugs on our issue tracker:
https://github.com/wurmlab/sequenceserver/issues

Upgrading is simple. If you have ruby 2.3 or later, run:

gem install --pre sequenceserver

This does not remove your current sequenceserver installation. Instead, it changes
the default. If something breaks, you can rollback by running:

gem uninstall sequenceserver

We welcome any help you may be able to provide in terms of code review,
improving test coverage, and making code style checkers happy.

Kind regards,
Priyam & Yannick