Work Item Triage

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.

Close

Code Freeze

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.

Close

Release Candidate 1

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.

Close

Release Candidate 2

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.

Close

Release Candidate 3

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

Close

Web Posting

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.

Close

Linxter Beta 2

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

Close

Linxter Beta 3

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

Close

Linxter Beta 3.1

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

Close

Linxter v 1.0

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

Close

Linxter v 1.0 SP1

What's New:

• Faster program instance registration
• Improved message sending performance
• Company account usage reports broken out by month
• Logging of program setting changes
• Context sensitive help when registering program to ISB
• Web Manager UI improvements

Close

Linxter v 1.1

What's New:

• Ability for program instances to use both TCP and HTTPS as the transport protocol
• Instance load balancing groups - When a message is is received by a Load Balance Group, the ISB randomly selects one of its members to send the message to. Useful if you are dealing with a high volume messages and want to distribute the processing of those messages among multiple program instances.
• Support for message prioritization within queues
• Support for one to many local API queues for outgoing messages within a single program instance, each queue with unique sending settings
• ISB and SDK API performance improvements
• Ability to customize connection retries, both the number of them and the time interval in between
• Simplified API integration - developer will not have to enter IDs, but instead select the program and IDs will be pulled in
• Ability to permanently disable a program instance
• COM visibility for SDK API

Close