Our first step in the development cycle process is to conduct a "triage" to review all of the Work Items requested by both members of the Linxter team and by customers. They are ranked by importance based on criteria associated with the Work Item type. We also weigh the risk to code stability and architectural limitations. Because of the schedule-driven nature of releases, not all Work Items can be addressed immediately.

Code Freeze is the developers' deadline for submitting fixes. Declaring code freeze is necessary to give the Quality Engineering team the needed time to conduct feature testing, server reliability testing, and regression testing. Testing is ongoing throughout the product cycle.

At this point in the process all Work Items have been verified and regression testing continues. Using Release Candidate 1 we focus our testing on reliability in a production environment.

Our Release Candidate 2 build is the code that we feel is ready for the final testing before we consider this release completed. At this point in the process all Work Items have been verified, final regression testing has been completed, and reliability has been proven.

At this point in the process, final testing has been completed. The Release Notes and other documentation associated with the release is verified.

If applicable, the updated SDK is posted on our website and the production ISB is updated. Product quality is our number one goal so if we find that the product does not pass Quality Engineering testing, we may choose to hold the release of the product until our testing shows that the product meets our quality goals.

What's New:

• Overhauled the Linxter Web Manager user interface
• Updated the HelloWorld Visual Studio Template
• Added a Standard Linxter Integration Visual Studio Template
• Added the ability to have communication channel requests automatically created when a program instance is activated
• Updated the Getting Started documentation

What's New:

• Reorganization of methods for on demand and scheduled sending and receiving
• Enhancements to Web Manager user interface
• Web Manager support for both IE and Firefox
• Standardization of API local datastore to SQLite
• Availability of Quick Start 1
• Chunking support for file attachments

What's New:

• Final reorganization of methods, properties and events
• Availability of Quick Starts 1, 2, 3 and 4
• Support for local instance management of communication channels

What's New:

• 10x performance increase in message retrieval
• Message tracking option - receive date/time a message you sent was picked-up by the recipient program instance
• Ability to export and import program settings via an XML file
• Quick Starts 1 - 4 available in both C# and VB

What's New:

API

• Improved message sending performance
• Added new method, CreateMessages(), used for creating a large number of messages in a short period of time
• ClickOnce deployment now supported

Web Manager

• Company account usage reports broken out by month
• Logging of program setting changes
• Context sensitive help when registering a program to ISB
• General UI improvements

What's New:

API

• Simplified Linxter Integration - using the wizard integration template, developers no longer have to copy and paste their IDs, they can select their program from a list and the IDs will be auto-populated
• Updated Hello World sample to send messages to itself

Open Source Samples

• The addition of Linxter Messenger, a desktop messenger sample application.

What's New:

ISB

• This release is primarily focused on back-end performance and reliability improvements

Web Manager

• Export IDs button - the name of the program has been added to the default export file name

What's New:

API

• Simplification of file attachment retrieval
• ChannelRequestInfo Member CreatedDate added - For outbound request, this is the local system date/time the request was sent. For an inbound request, this is the local system date/time the request was received.
• Improvements to sending and retrieval speed

Web Manager

• Support module added - submit feature requests & bugs
• Bug fix - when you change a program's allowed comm. channels, when that change conflicts with existing channels, the no longer legitimate channels will be closed

What's New:

API

• Bug fix for the locking of APIs encrypted database

ISB

• Improved message retrieval speed

What's New:

API

• All messages autmoatically encrypted with X.509 certificates
• Ability for program instances to use both TCP and HTTP as the transport protocol
• Improved message sending performance
• Support for message prioritization within queues
• Optional secondary local API queue for outgoing messages
• Ability to permanently disable a program instance remotely
• FindProgramInstances method expanded to allow for search criteria concatenation

What's New:

API, ISB and Web Manager

• SDK's Integration Wizard updated to work with Visual Studio 2010
• Change to ISB service authentication from custom implementation to Active Directory.

What's New:

API

• A memory leak has been fixed
• SDK performance improvements
• Upgrade of SDK's local encrypted datastore from SQLite version 3.6.17 to 3.6.23.1

What's New:

API and ISB

• Performance improvements with the sending and receiving of file attachments

What's New:

API and ISB

• Bug fix for SDK when running in Azure

What's New:

API and ISB

• Commercial release of Android SDK

What's New:

API and ISB

• Commercial release of Java SDK

What's New:

New Features

• Audit copy — allows companies to fulfill compliance requirements when audit copies of messages their instances send and receive is required
• Privileged instance — enables developers to create an instance for a Program which receives all messages sent to all instances of that Program
• Re-release of CloudMiddleware.com, a cloud integration hub providing pre-built PaaS and SaaS integrations

Improvements

• ISB performance improvement through use of parallelism and reduction of broker database lookups

What's New:

Bugs Fixes and Improvements

• Fixed a bug across all SDKs that kept the ProgramInstanceActivated Event from getting raised when the instance was auto-activated.
• In the .NET, Android, and Java SDK, added SQLite Vacuum command on instance startup to reclaim any "free" space that may exist.
• In the Android and Java SDK, fixed a bug causing intermittent failure to send messages when file attachments were added.
• In the .NET and WP7 SDK, changed all of the interface implementations from explicit to implicit on the LinxterSDK class. This allows developers to ignore the interfaces if desired and program just against the public API of the LinxterSDK class. This is already the case in our Android and Java SDKs.

What's New:

Bug Fixes in Java and Android SDKs

• In the Java and Android SDK, fixed the init code to run internal SDK performStartupTasks() asynchronously, resulting in a performance improvement.
• In the Java and Android SDK, fixed ISB service ping so it runs on a separate asynchronous thread, resulting in a performance improvement.