potiuk opened a new pull request, #63305:
URL: https://github.com/apache/airflow/pull/63305

   Split the monolithic `PROVIDERS.rst` into focused documents under the 
`providers/` folder,
   alongside the existing `MANAGING_PROVIDERS_LIFECYCLE.rst`.
   
   ## Summary
   
   - Keep `PROVIDERS.rst` as a concise hub with overview, document index table, 
and stub sections
     preserving all existing anchor links (used by hundreds of changelog files)
   - New documents under `providers/`:
     - `PROVIDER_GOVERNANCE.rst` - governance framework, stewardship, lifecycle 
stages, health metrics
     - `ACCEPTING_PROVIDERS.rst` - prerequisites and approval process for new 
providers
     - `PROVIDER_RELEASES.rst` - release process, SEMVER versioning, 
distribution states, min Airflow version
     - `SUSPENDING_AND_REMOVING_PROVIDERS.rst` - suspension and removal 
criteria/process
     - `THIRD_PARTY_PROVIDERS.rst` - 3rd-party providers and mixed governance 
model
   - Restructured `MANAGING_PROVIDERS_LIFECYCLE.rst` with consistent heading 
hierarchy and logical
     section grouping (creating, releasing, suspending, resuming, removing)
   - Updated all cross-references between documents
   
   ## Test plan
   
   - [ ] Verify all existing anchor links from changelog files still resolve 
correctly
   - [ ] Verify cross-references between the new documents work
   - [ ] Build docs with `breeze build-docs apache-airflow` to check for broken 
links
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Opus 4.6
   
   Generated-by: Claude Opus 4.6 following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to