By prasads on Dec 23, 2007
Project Sailfin is expected to deliver its first release of the Communications Application Server , in June of 2008. The schedule is based on a milestone model wherein, each milestone corresponds to a set of features added. This helps dividing up the dependencies to be satisfied first in the earlier milestone, and also helps in planning of resources.
We hit Milestone 3 on Dec 10th 2007, and a certified binary corresponding to the Milestone 3 features has been made available since Dec 22nd.
So what does a certified binary mean ?
Typically a certified binary has has series of regression tests, sanity tests run. These tests validate the basic container level features such as that of the SIP Container, EJB Container, Web Container. In addition that the Java EE TCKs are run to make sure that the Application Server remains compliant to the Java EE spec. In case of the Milestone builds of Sailfin, key functional tests corresponding to the new features are also used to certify the builds. This helps us isolate the known issues in these new features and also to propose workarounds.
What's new in MS3 ?
The main features that got delivered in this Milestone are in the areas of Deployment, Administration and Monitoring of the SIP Container, CLB (Converged Load Balancer), Security .There were also features in Session replication that are available now, but the plan is that Session Replication is expected to be completed only by Jan 21st 2007. Here is a list of features with some details.
Support for Annotations in JSR289
Annotations like SipSessionListener, SipApplicationKey, SipApplication, SipSessionAttributeListener, SipServletListener,
Administration for SIP Container
Monitoring of the SIP Container
What's next ?
Our next milestone is on Jan 21st 2008 which is the feature freeze date for all modules including Session Replication and JSR289 based SIP Container. There is a small caveat as far as JSR289 based container goes, since the spec. has not gone final yet, one can never say that the code has been frozen till the spec is final. Hence the plan for JSR289 based container is to get the code as close to the JSR289 PR draft as possible.
The feature freeze on January 21st would be the freeze for the beta release of Sailfin, due in March of 2008. We are looking to stabilize the features that have come in , between now and Jan 21st. Any and every feedback that comes would contribute towards the quality of the product. The detailed schedule is available here
Getting the binary
The Milestone3 binary can be obtained from here.
One can also navigate through the download link on the Sailfin site to the download page, where
Nightly Builds ( unstable , built every night )
Promoted Builds ( stable , built every week )
Milestone Builds ( stable and certified )
can be downloaded.
Bugs are expected and we welcome them and they can be filed at IssueTracker