Currently, ExLibris releases new Rosetta versions by announcing a rough release date ("April this year"), publishing the version, minor release, servicepack, or hotfix, and providing a list of changes. ExLibris will only provide a very basic roadmap of the anticipated improvements until the actual release. Customers find it difficult to get ready for the release, even if this is an easy strategy for ExLibris. In order to allow developers to modify their software (i.e., Submission Applications) to accommodate new features, altered API behavior, etc., I thus suggest that ExLibris offer pre-release versions of Rosetta. As has been a best practice across the industry for many years, these beta versions might also be used to get user input on the modifications and enhance features prior to the final release.

I propose that ExLibris at least publish their interface description for new APIs so that developers can start working on their projects before the official release, in case the recommended developer preview releases are not possible for any reason. API interfaces should be accessible from the outset since they must be described at a very early stage of the design process. Before the release, developers could write their routines and mock answers; they would only need to do a few last tests once the real, functional API was made accessible.
Drift Boss