Jinwoo Hwang created GEODE-10512:
------------------------------------

             Summary: Create Support Branch for Apache Geode 2.0
                 Key: GEODE-10512
                 URL: https://issues.apache.org/jira/browse/GEODE-10512
             Project: Geode
          Issue Type: Task
            Reporter: Jinwoo Hwang
            Assignee: Jinwoo Hwang
             Fix For: 2.0.0


As part of the Geode 2.0 release preparation, we need to review and update the 
LICENSE and NOTICE files to ensure all dependencies and third-party components 
are accurately documented before cutting the support branch.
h2. Tasks
h3. 1. License Review Script

Check LICENSE files for:
 * Missing dependencies
 * Outdated versions
 * Dependencies removed since the previous release

h3. 2. Review Dependencies Changes
 * Identify any new dependencies added since Geode 1.15.2
 * Check if any dependencies were removed and manually verify if stale 
references exist in LICENSE or NOTICE files that can be removed
 * For new dependencies with Apache 2.0 License, add them to the {{isApache2}} 
function in the license_review script

h3. 3. Update Binary Distribution License

If any new 3rd-party .jar files now appear in the binary distribution, update 
{{geode-assembly/src/main/dist/LICENSE}} accordingly
h3. 4. Update Source Tree License

If new 3rd-party intellectual property was checked into the source tree (e.g., 
JavaScript libraries, CSS files, etc.), update:
 * Root {{LICENSE}} file
 * {{geode-assembly/src/main/dist/LICENSE}} file

h3. 5. Review NOTICE File
 * Verify all copyright notices are current and accurate
 * Ensure all required attributions for third-party components are present

h2. Acceptance Criteria
 * All new dependencies are properly documented in LICENSE file(s)
 * All removed dependencies have been cleaned up from LICENSE/NOTICE files
 * Binary distribution LICENSE is accurate
 * Source tree LICENSE includes all checked-in third-party code
 * NOTICE file contains all required copyright and attribution notices
 * Changes are committed to develop
 * Review discussed with community on dev list if any questions arise

h2. Notes
 * This should be completed before cutting the support/2.0 branch
 * This is a critical step for Apache compliance and release approval



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to