Documentation Archive Developer
Search

ADC Home > Reference Library > Technical Q&As > Legacy Documents > Carbon >

Legacy Documentclose button

Important: This document is part of the Legacy section of the ADC Reference Library. This information should not be used for new development.

Current information on this Reference Library topic can be found here:

NOTE: This Technical Q&A has been retired. Please see the Technical Q&As page for current documentation.

New MacApp Release Approach


Q: Why is Apple now making the latest versions of MacApp available under a Release approach, instead of the previous Product Approach?

A: In response to the many messages we received from developers requesting early access to new framework features and timely support for new technologies, Apple has implemented a Release approach with MacApp that allows us to get new improvements and features in our frameworks into your hands more quickly than was possible with the Product approach.

Previous to the Release approach, our Product approach required that we implement all planned features before the MacApp product was considered final. We found that the Product approach was keeping us from getting new features to you simply because other more time-consuming work was delaying the completion of the product. Under the new Release approach, each framework release will be made up of features at various levels of certification. Most features will be of final quality, while others may be of beta or alpha quality. You can choose the features with which to build your MacApp-based application, and by doing so you will choose the quality level of the resulting application. Our build tools will indicate the quality level you have chosen from those build flags you have passed to them. The release notes which accompany each MacApp release will list the features included in the framework and their quality status.

Important: For each MacApp release, ALWAYS refer to the release notes for the quality status. For some releases, we recommend that you do not build applications which you intend to rely on as "final" quality applications. Releases that have final quality status are suitable for building final-quality MacApp-based applications.

Over the course of multiple releases, every feature will proceed through alpha, beta, and final quality phases. Some features will move rapidly from development into final quality, perhaps in as little time as one release, while other features may require several releases. This approach ensures that the software features Apple provides to you are of the highest possible quality, while still allowing you to experiment with new, unproven features.

In addition to giving you an early indication of the direction Apple is taking with MacApp, the release approach will also improve the timeliness of Apple's support for new technologies, because feedback regarding your needs and requirements can direct which module we enhance first.

Apple will create a new Release version of MacApp approximately once every six to nine months, and the MacApp product will ship once each ETO delivery cycle. Releases of MacApp that occur between ETO shipment dates will be posted to the Web.

[Aug 21 1996]