Username:
Password:
Please type the Two words with a space between them to prove you are a real human being.
3SL is pleased to announce that we released Cradle-6.1 in November 2009. This is the latest new release of our requirements management and systems engineering environment and is a minor enhancement to previous releases. Cradle-6.1 is a full product release, and is accompanied by completely re-written documentation and related materials.
The Cradle-6.1 release provides a small number of enhancements and some bug fixes to the major Cradle-6.1 release. For a detailed list of all enhancements and bug fixes that is also grouped by Cradle module, please consult:
The major improvements in the Cradle-6.1 release are:
Cradle-6.1 has a new format for its project databases. If you upgrade to Cradle-6.1 you must convert all your project databases to the new format. A converter is supplied with the release that will perform the conversions for you. The Cradle-6.1 installers automatically detect the need to run this converter, to ensure that the upgrade is as simple as possible.
It is also possible to upgrade to a new release by creating a new Cradle installation with new project databases in new directories and using exports and imports to move data between the databases of the old and new versions. With this approach, you could use the new version and its databases, or you could revert to the old Cradle version and its databases. These two sets of databases would initially have the same contents, but this would remain true only for so long as data is not changed in one set that is not also changed in the other.
Customers who adopt this approach use a procedure similar to:
We always recommend using the database converters that are supplied with Cradle.
If you are updating to Cradle-6.1 from Cradle-5.2, or any later version, then you can use either approach. That is, you can either convert Cradle-5.2 (or later) databases to Cradle-6.1 or you can export from Cradle-5.2 (or later) and import into Cradle-6.1. We recommend that you use the conversion approach, but the choice is yours.
However, if you are updating to Cradle-6.1 from Cradle-5.1 (or one of its updates) or an earlier release then you must read the next section very carefully.
This section ONLY applies to those customers who are upgrading to Cradle-6.1 directly from Cradle-5.1 (or one of its updates) or from an earlier version.
If you have not used change histories (edit histories) in the earlier version of Cradle, then you can still use the export-and-import approach to the upgrade to Cradle-6.1 described in the previous section, if you wish, but if you decide to use this approach, please also read the following section about upgrading from Cradle-5.7, as this will apply to you as well.
However, if you have used change histories (edit histories) in Cradle-5.1 (or any of its updates) then you must use the converter to upgrade to Cradle-6.0.
At Cradle-5.2 we changed the way change histories (edit histories) are stored. Prior to version 5.2, they were stored in the project Configuration Log used in the Cradle Configuration Management System (CMS). From version 5.2 they are stored in CHANGE HISTORY frames in the items in the database. Therefore, simply exporting and importing will not convert the change history information from the Configuration Log to CHANGE HISTORY frames, and so if you simply export from Cradle-5.1 and import into Cradle-6.1, then you will lose your change history information when viewed through Cradle-6.1.
Please be advised that in Cradle-6.0 we changed the internal representation of text inside frames, so that it better supports the concept of paragraphs and is far less based on the concept of text being a list of lines. This means that the database converter for Cradle-6.0, the executable cvt_5760.exe, performs some text manipulations as part of the database conversion. If you export from Cradle-5.7 and import into Cradle-6.1, then these text manipulations will not occur. You may therefore find a difference between a database conversion and an export followed by an import.
From Cradle-6.0 onwards, the Toolset client was completely removed. This means that:
So in summary Cradle is no longer supplied with any fonts for any platform.
Cradle-6.1 has some enhancements and several bug fixes. It is a minor improvement over Cradle-6.0. It is a major improvement over Cradle-5.7.
We would like you to use Cradle-6.1 in preference to Cradle-5.7 or any earlier version. That is why we have released it!
If you are currently using Cradle-6.0, there is no immediate need to upgrade to Cradle-6.1, but you should consult the Cradle-6.1 Release Notes to see if any of the enhancements or bug fixes are relevant to you.
If you are currently using Cradle-5.7, then we very strongly recommend that you upgrade to Cradle-6.1 (not Cradle-6.0) as Cradle-6.1 represents a very substantial improvement when compared to Cradle-5.7.
3SL will continue to support Cradle-5.7 until the next major version of Cradle is released.
However, if you are using Cradle-5.6, or an earlier release, then we urge you to upgrade to Cradle-6.1 because:
You will see some dramatic extensions and improvements
3SL no longer supports these releases
You cannot mix Cradle-6.1 with any earlier release of Cradle. This means that if you decide to install Cradle-6.1 anywhere, then you must install it everywhere.
Specifically:
Cradle-6.1 servers will not respond to Cradle-6.0 or earlier clients
Cradle-6.1 clients will not be serviced by Cradle-6.0 or earlier servers
These incompatibilities are failsafe. That is, if you should accidentally fail to upgrade a client to Cradle-6.1, then starting that client will not adversely effect the operation of Cradle-6.1, as the Cradle-6.1 servers will ignore connection attempts from clients of any previous version.
All Cradle-6.1 download files for Windows and UNIX were added to our website and to our mirror site on 14 th November 2009.
For Windows, the file to download is: Cradle61_Setup.exe
Note that Cradle-6.1 only supports 32-bit Windows platforms. Including Windows Vista.
For UNIX, your must download the boot and core.Z filesets, and also download the fileset that contains the executable files for your architecture:
So, if you are running on UNIX, you will need to download a minimum of 3 filesets.
If you have a UNIX server that provides executables for multiple architectures, then you will need to download boot, core.Z and filesets for all architectures provided by your server.
If you are running a mixed UNIX and Windows environment, such as UNIX servers and Windows clients, then you will need to download the Windows self-extracting executable and all UNIX filesets that are needed for your environment.
3SL has a dedicated 8 Mbit/sec Internet connection which means that the largest of these files can be downloaded in 6 minutes. Our mirror site provides even faster downloads.
Back to the newsletter archive.
