Development lifecycle（开发生命周期）¶
At Palantir, we strive to continuously evolve production-grade software to meet the needs of our customers and improve the capabilities we offer. We incorporate cutting-edge technologies and frameworks while remaining grounded in the real-world problems our customers face every day. In practice, this means that Palantir can develop new capabilities in close partnership with customers.
This page outlines the various development life cycle phases of capabilities in the Palantir platform, including the definitions of these statuses, their availability, support levels, and the expectations we set for those statuses between Palantir and our customers.
:::callout{theme="warning"} While this page explains the typical execution of the product development life cycle at Palantir, some attributes of a life cycle phase may vary based on a given product or feature. :::
Phases of development: Summary¶
This table provides an overview of the different development statuses and their core attributes. For more information, see the linked detail sections on each status.
| Status | Development | Availability | User support | Public documentation |
|---|---|---|---|---|
| Experimental: Prototype or exploratory feature | 🟢 Active | 🔴 Very limited availability | 🔴 None | 🔴 None |
| Beta: Early-stage feature with a typically slower rollout | 🟢 Active | 🟡 Opt-in availability | 🟢 Yes | 🟢 Yes |
| Generally available (GA): Production feature | 🟢 Active | 🟢 Broadly available | 🟢 Yes | 🟢 Yes |
| Legacy: Production feature without active development | 🟡 Critical fixes only | 🟢 Broadly available * | 🟢 Yes | 🟢 Yes |
| Sunset: Feature slated for deprecation, but no date is scheduled | 🟡 Critical fixes only | 🟡 Existing customers only | 🟢 Yes | 🟢 Yes |
| Planned deprecation: Deprecation date and migration path communicated | 🟡 Critical fixes only | 🟡 Existing customers only | 🟢 Yes | 🟢 Yes |
| Deprecated: Feature is no longer available | 🔴 None | 🔴 None | 🔴 None | 🔴 None |
* Installed but disabled for new customers by default. New customers can enable the feature through Control Panel.
Phases of development¶
Experimental¶
New features in Foundry begin in an experimental or prototype phase.
These features and products are in the early stages of development and are typically worked on in collaboration with a small set of customers. The goal of the experimental phase is to demonstrate and validate a new capability as quickly as possible. Features in the experimental phase may not be publicly documented, as we prioritize speed of development to explore the space of solutions expansively. Experimental products are expected to change frequently and may not progress to other life cycle stages.
Beta¶
Once a feature's purpose and approach has been validated with one or more customer partners, it is made available to a broader group of customers in a beta phase.
The goals of the beta phase are to invest heavily in the long-term maintainability of a feature while measuring overall value and usage. For this reason, beta features may be rolled out slowly to customers to gather feedback during the development process. Sometimes, beta features are available to a wide range of customers; at other times, beta features may be limited to partners with specific business needs or feedback opportunities that advance the development process.
Beta features are documented publicly to help enable customer partners to use this early-stage functionality, even if the features are not yet available in every enrollment. When a feature is in the beta phase, it will be labeled as such in documentation.
There is no guarantee that beta features or products will progress to the next stages of development, though the vast majority do move on to general availability.
Generally available (GA)¶
Generally available is the term used to describe the vast majority of features and products in Foundry. GA features are enabled for customers by default and constitute a core part of the platform. When features become GA, other parts of the platform may build on top of them to enable tight-knit integrations.
In the GA phase, there is a continuous feedback loop between Palantir engineers and the broad set of customers using the feature. Feedback is triaged, prioritized, and fed into Foundry's product roadmap, and updates are delivered to customers rapidly using Apollo ↗, Palantir's platform for continuous delivery.
Although GA features are widely available, it is possible in some cases that your enrollment may not have every feature enabled as some features have dependencies on specific types of infrastructure or may require specific contractual agreements. For example, some GA features in Foundry are only available in Palantir's managed SaaS environment and are not supported for self-hosted installations. Keep in mind that when a new feature or application is announced as generally available, there may be a delay of a week or more before it becomes available within a specific Foundry enrollment.
Unless otherwise specified, any publicly documented feature is generally available, and you can rely on GA features to be fully supported. The removal of any GA feature from the platform will follow the sunset and planned deprecation processes outlined below.
Legacy¶
In the legacy phase of development, features and products enter a stage where work is considered complete and no additional feature development is expected.
Legacy applications are widely installed across the Palantir customer base and available for continued production use. As in GA, products in the legacy status remain fully supported. For new customers, they are typically available on an opt-in basis. Despite legacy features not being actively developed, feedback is still encouraged as it can inform our work on new applications and tools.
All products and features in the legacy phase will be labeled as such and thoroughly documented publicly. At this point, no deprecation date is planned or expected.
Sunset¶
As development progresses, an existing feature or application in Foundry may reach the end of its usefulness or purpose, or it may be superseded by another functionality. The original vision for the feature may be narrower than the problem space it has grown to address, or new tools or features may result in more robust or scalable solutions to a problem. At this point, we start to discourage use of the feature, and new customers will not be able to enable it for use in their enrollment.
In our public documentation, we will label products that are in the sunset phase and will suggest other tools and applications to replace them. As in GA, products in the sunset phase remain fully supported. Deprecation is planned for the future, but no exact date is confirmed. As soon a deprecation date is identified, the feature will move into the planned deprecation phase, with the date and any relevant migration details communicated.
Planned deprecation¶
Products entering the planned deprecation phase are preparing for retirement from the platform. As products or features enter the planned deprecation phase, Palantir works to provide proactive communication around the scheduled retirement date and any migration steps, if needed. Products in planned deprecation remain fully supported. However, new enrollments will not be able to enable features in planned deprecation.
In planned deprecation, a feature does have a confirmed deprecation date, and we are in the process of removing the feature and its integrations from our platform. Like products in the sunset phase, we will label products in the planned deprecation in our public documentation and in the platform. Our public documentation will also offer suggestions for workflow migrations that will fit your use case.
When we move a feature into planned deprecation, you can expect time to migrate your workflows to new tools and applications before the scheduled deprecation date. We will use our platform Upgrade Assistant to notify administrators of the upcoming deprecation and provide a clear deadline for complying with workflow migrations. For application-level deprecations, the intent to deprecate and the final deprecation notice will be proactively shared with the registered platform administrator's contact details as well as publicly on the Foundry Announcements page. Progress towards feature deprecation is tracked quantitatively to ensure all customers are able to migrate to a replacement before a feature is finally removed from the platform.
Deprecated¶
When a product completes the required tasks during the planned deprecation phase, it is considered fully deprecated. In this phase, the feature or product is no longer supported or available in the platform and all customers have been migrated away from relevant workflows. Customers will no longer have access to related API endpoints or other integrations, and support is no longer available. All public documentation of the feature is removed and no longer discoverable.
中文翻译¶
开发生命周期¶
在Palantir，我们致力于持续演进生产级软件，以满足客户需求并提升我们提供的能力。我们融合前沿技术与框架，同时始终立足于客户每天面临的真实问题。在实践中，这意味着Palantir能够与客户紧密合作，共同开发新能力。
本页概述了Palantir平台中各项能力的各个开发生命周期阶段，包括这些状态的定义、可用性、支持级别，以及Palantir与客户之间对这些状态的期望。
:::callout{theme="warning"} 虽然本页说明了Palantir产品开发生命周期的典型执行方式，但生命周期阶段的某些属性可能因特定产品或功能而异。 :::
开发阶段：概览¶
下表概述了不同的开发状态及其核心属性。有关更多信息，请参阅每个状态的详细说明部分链接。
| 状态 | 开发 | 可用性 | 用户支持 | 公开文档 |
|---|---|---|---|---|
| 实验性(Experimental)：原型或探索性功能 | 🟢 活跃 | 🔴 可用性非常有限 | 🔴 无 | 🔴 无 |
| 测试版(Beta)：通常缓慢推出的早期功能 | 🟢 活跃 | 🟡 选择加入可用性 | 🟢 有 | 🟢 有 |
| 正式发布(GA)：生产功能 | 🟢 活跃 | 🟢 广泛可用 | 🟢 有 | 🟢 有 |
| 遗留(Legacy)：无活跃开发的生产功能 | 🟡 仅限关键修复 | 🟢 广泛可用 * | 🟢 有 | 🟢 有 |
| 日落(Sunset)：计划弃用但未确定日期的功能 | 🟡 仅限关键修复 | 🟡 仅限现有客户 | 🟢 有 | 🟢 有 |
| 计划弃用(Planned deprecation)：已传达弃用日期和迁移路径 | 🟡 仅限关键修复 | 🟡 仅限现有客户 | 🟢 有 | 🟢 有 |
| 已弃用(Deprecated)：不再可用的功能 | 🔴 无 | 🔴 无 | 🔴 无 | 🔴 无 |
* 已安装但默认对新客户禁用。新客户可通过控制面板(Control Panel)启用该功能。
开发阶段¶
实验性(Experimental)¶
Foundry中的新功能始于实验性(Experimental)或原型阶段。
这些功能和产品处于开发的早期阶段，通常与少量客户合作开发。实验阶段的目标是尽可能快速地演示和验证新能力。处于实验阶段的功能可能没有公开文档，因为我们优先考虑开发速度，以广泛探索解决方案空间。实验性产品预计会频繁变更，并且可能不会进入其他生命周期阶段。
测试版(Beta)¶
当一个功能的目的和方法已与一个或多个客户合作伙伴验证后，它将在测试版(Beta)阶段向更广泛的客户群体开放。
测试阶段的目标是在衡量整体价值和用量的同时，大力投资于功能的长期可维护性。因此，测试版功能可能会缓慢向客户推出，以便在开发过程中收集反馈。有时，测试版功能可供广泛客户使用；其他时候，测试版功能可能仅限于具有特定业务需求或反馈机会的合作伙伴，以推动开发进程。
测试版功能会公开记录文档，以帮助客户合作伙伴使用这些早期功能，即使这些功能尚未在每个注册环境中可用。当功能处于测试阶段时，文档中会相应标注。
无法保证测试版功能或产品会进入下一开发阶段，尽管绝大多数最终会进入正式发布阶段。
正式发布(GA)¶
正式发布(Generally available, GA)用于描述Foundry中绝大多数功能和产品。GA功能默认对客户启用，构成平台的核心部分。当功能成为GA后，平台的其他部分可以在此基础上构建，以实现紧密集成的整合。
在GA阶段，Palantir工程师与使用该功能的广大客户之间存在持续的反馈循环。反馈会被分类、优先级排序，并纳入Foundry的产品路线图，更新通过Palantir的持续交付平台Apollo ↗快速交付给客户。
尽管GA功能广泛可用，但在某些情况下，您的注册环境可能未启用所有功能，因为某些功能依赖于特定类型的基础设施，或需要特定的合同协议。例如，Foundry中的某些GA功能仅在Palantir托管的SaaS环境中可用，不支持自托管安装。请注意，当新功能或应用程序宣布正式发布时，可能需要一周或更长时间才能在该特定Foundry注册环境中可用。
除非另有说明，任何公开文档记录的功能均为正式发布，您可以依赖GA功能获得完全支持。从平台中移除任何GA功能将遵循下文概述的日落和计划弃用流程。
遗留(Legacy)¶
在遗留(Legacy)开发阶段，功能和产品进入工作已完成且预计不再进行额外功能开发的阶段。
遗留应用程序广泛安装在Palantir客户群中，可供继续生产使用。与GA一样，处于遗留状态的产品仍获得完全支持。对于新客户，它们通常以选择加入的方式提供。尽管遗留功能没有积极开发，但仍鼓励提供反馈，因为这可以为我们开发新应用程序和工具提供参考。
所有处于遗留阶段的产品和功能都将被相应标注，并公开提供完整文档。此时，没有计划或预期弃用日期。
日落(Sunset)¶
随着开发的推进，Foundry中的现有功能或应用程序可能达到其有用性或目的的终点，或被其他功能所取代。该功能的原始愿景可能比它已发展解决的问题空间更窄，或者新工具或功能可能为问题提供更稳健或可扩展的解决方案。此时，我们开始不鼓励使用该功能，新客户将无法在其注册环境中启用该功能。
在我们的公开文档中，我们将标注处于日落阶段的产品，并建议其他工具和应用程序作为替代。与GA一样，处于日落阶段的产品仍获得完全支持。未来计划弃用，但尚未确认确切日期。一旦确定弃用日期，该功能将进入计划弃用(Planned deprecation)阶段，并传达日期和任何相关的迁移细节。
计划弃用(Planned deprecation)¶
进入计划弃用(Planned deprecation)阶段的产品正准备从平台中退役。当产品或功能进入计划弃用阶段时，Palantir会主动沟通预定的退役日期以及任何必要的迁移步骤。处于计划弃用阶段的产品仍获得完全支持。但是，新注册环境将无法启用处于计划弃用阶段的功能。
在计划弃用阶段，功能确实有确认的弃用日期，我们正在从平台中移除该功能及其集成。与日落阶段的产品一样，我们将在公开文档和平台中标注处于计划弃用阶段的产品。我们的公开文档还将提供适合您用例的工作流迁移建议。
当我们将功能移入计划弃用时，您可以预期在预定弃用日期之前有时间将您的工作流迁移到新工具和应用程序。我们将使用平台升级助手(Upgrade Assistant)通知管理员即将到来的弃用，并提供遵守工作流迁移的明确截止日期。对于应用程序级别的弃用，弃用意图和最终弃用通知将主动与注册平台管理员的联系信息共享，并在Foundry公告页面上公开。功能弃用的进展会进行量化跟踪，以确保所有客户都能在功能最终从平台移除之前迁移到替代方案。
已弃用(Deprecated)¶
当产品在计划弃用阶段完成所需任务后，即被视为完全已弃用(Deprecated)。在此阶段，该功能或产品不再受支持或在平台中可用，所有客户已从相关工作流迁移。客户将不再能够访问相关的API端点或其他集成，也不再提供支持。该功能的所有公开文档均被移除且无法再被查找。