Skip to main content
Version: 8.4.10.2

Software Release Cycle

Development​

SpiderRock Connect is a platform under continuous development. We utilize a rapid development cycle where fixes and features are created and tested in short 2-4 weeks sprints and are released as packages during Saturday maintenance windows.

Testing​

Prior to release, the system is tested by our dedicated release QA team and previewed by our Client Support Desk. We run staging (preview) versions of our code in a limited stripe system environment (Venus) prior to release. This environment is sometimes available to clients who have a need to test and release code simultaneously with us.

We have an extensive set of integration/regression tests that we run against our pre-release code base. This test suite particularly covers our execution engines but also has coverage for all of the other parts of the system.

Notification​

During the week prior to an expected production software release, SpiderRock will disseminate Release Notes for the upcoming release. The notes will detail any new features and bug fixes that are planned in the upcoming release package, as week as any MBus and FIX changes that may affect the clients.

Release​

We release code for our production environment globally and simultaneously during normal release windows. This establishes a new common code baseline for all system realms (regions) within our production system environment. During these normal release windows we may make changes to our schemas and record/message layouts. Generally these schema changes involve adding message types, fields, or enum values which we expect our clients to be able to automatically handle in their systems. Occasionally, we make changes that are not backward compatible (eg. deprecating message types or fields or removing values from enums). We attempt to both minimize these 'breaking' changes and make clients aware of them in advance. We also, occasionally, make 'hotfix' releases to some part of our production environment. Hotfix releases never include changes to our schemas and we attempt to give as much notice as possible if or when we make this types of release.

Bug Reports​

We appreciate bug reports and do address them in as timely a fashion as possible. If you report a system bug to our Client Support Desk, we will create an appropriate ticket which will get tracked and managed through our normal release process (or, if high enough priority, our hotfix process). Feel free to inquire about progress on bug or issues at any time.