From a1ee65d277d6a460df3681b446ee475b4d972ac1 Mon Sep 17 00:00:00 2001 From: Zack Koppert Date: Mon, 30 Jun 2025 17:40:28 -0700 Subject: [PATCH] docs: update formatting Signed-off-by: Zack Koppert --- policies/releasing.md | 1 - 1 file changed, 1 deletion(-) diff --git a/policies/releasing.md b/policies/releasing.md index 5d96c9e..dc34863 100644 --- a/policies/releasing.md +++ b/policies/releasing.md @@ -16,7 +16,6 @@ The following steps should be taken to release and maintain your open source pro - **SECURITY.md file** including instructions that enable users to privately report security vulnerabilities found in your project. 4. **Prepare the code for release**. - - **Code license**. MIT is the preferred license - other licenses must be cleared with legal. - **Remove sensitive assets**. - Remove any reference in the code to internal or confidential information, including internal paths, tools, codenames, proprietary fonts, internal telemetry and email aliases.