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

   This PR adds possibility of marking the provider as "not ready" in the 
provider.yaml (by setting optional field as "not-ready" to `true".
   
   Setting provider as "not-ready", removes it by default from all the release 
management commands - preparing documentation files preparing provider 
packages, publishing docs.
   
   You can include such providers via `--include-not-ready-providers` flag (or 
setting INCLUDE_NOT_READY_PROVIDERS environment variable to true).
   
   This flag is set to True in our CI, so that we can make sure the providers 
in-progress are also being tested and verified, but when release manager 
prepares packages, those providers are not prepared.
   
   That will help in early stage of a lifecycle of a provider when we already 
want to iterate and test it continuously, but - for example the API of such 
provider is not yet stable or when we are in progress of moving functionality 
for such provider from core.
   
   This PR also marks `fab` providers as "not-ready" as it is still early days 
and we want to exclude it for now from any kind of release process.
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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