diff --git a/docs/dev/guides/record-a-demo.md b/docs/dev/guides/record-a-demo.md deleted file mode 100644 index d494b103b2..0000000000 --- a/docs/dev/guides/record-a-demo.md +++ /dev/null @@ -1,18 +0,0 @@ -# Record a Demo - -If you are contributing a new feature or a substantive change, please record a short demo and provide a downloadable link or asciinema URL to the demo as part of your pull request. - -These short demos help the wider Pulp community grasp the latest changes in Pulp. They also provide an extra opportunity for feedback on changes. - -While demos with audio are more than welcome, audio is not required. - -If your demo involves only a terminal recording, feel free to use a tool such as [asciinema](https://asciinema.org/). - -If you use [asciinema](https://asciinema.org/), adjust your terminal window to 90x45 characters to maintain the consistency of each of the demos. - -You can also use [Saftladen](https://github.com/mdellweg/saftladen) - a bundle of scripts to generate asciinema demos for Pulp topics without live user interaction. - -If you think that your change is not substantive enough to require a demo, mention that in the body of the pull request. -However, those reviewing the pull request might ask you to record a demo if they think it would help the wider community understand the change. - -Please tag [@melcorr](https://github.com/melcorr) in the body of your pull request to alert her to add your new demo to the list of demos. diff --git a/docs/dev/guides/release_process.md b/docs/dev/guides/release_process.md deleted file mode 100644 index 4bbeeb8cc9..0000000000 --- a/docs/dev/guides/release_process.md +++ /dev/null @@ -1,25 +0,0 @@ -# Pulpcore Release Process - -Here are the steps to take to release a Pulpcore version: - -- A new Y-releases must take all steps. -- A new Z-release need only execute steps 2, 3, and 4. - -## Process - -- **"I am releasing a new Y-branch of Pulpcore (e.g., 3.23)"**: - - 1) Via the Github Actions, trigger a ["Create new release branch"](https://github.com/pulp/pulpcore/actions/workflows/create-branch.yml) job. -- **"I am releasing a new Z-release of Pulpcore (e.g., 3.23.0, 3.22.12)"**: - - 2) Via the Github Actions, trigger a ["Release pipeline"](https://github.com/pulp/pulpcore/actions/workflows/release.yml) job by specifying the release branch (X.Y) and the tag (X.Y.Z) of the release. - - 3) Once the release is available, make an announcement on Pulp discourse, in the "Announcements" category. See [example](https://discourse.pulpproject.org/t/pulpcore-3-21-0-is-now-available/626). - - 4) The CI automation will create PRs with the Changelog update and Versions bump that will need to be merged. -- **"I have released a new Y-release of Pulpcore, followup actions"**: - - 5) Arrange for a new oci-image for that release by following the ["oci-images Release Instructions"](https://github.com/pulp/pulp-oci-images/blob/latest/docs/developer-instructions.md). - - 6) Update the `ci_branches` stanza in [pulpcore's template.config.yml](https://github.com/pulp/pulpcore/blob/main/template_config.yml#L22). This stanza should always (and only) contain: - - The most-current (i.e., newly-released) branch. - - All branches in use by supported downstream products (see below). These are branches we will consider backporting selected bugfixes to. - - 7) Monitor [pulpcore pull-requests](https://github.com/pulp/pulpcore/pulls) for creation of a PR such as ["Update supported versions"](https://github.com/pulp/pulp-ci/pull/826). Such PRs are created by [this job](https://github.com/pulp/pulp-ci/actions/workflows/supported.yml). The job may have been disabled if there hasn't been any release-activity in the repository for at least 60 days. You will need to re-enable it in this case. - me possible failures of **Step 2**, above, include: - - If release-tag is new but not based on current-dev, workflow will complain and fail - - If release-tag is for an existing release (by accident) , the workflow won't fail until the docs-pub. Cleaning this up can be Exciting. - diff --git a/pulp_file/app/viewsets.py b/pulp_file/app/viewsets.py index 214d310f81..b2b80cac68 100644 --- a/pulp_file/app/viewsets.py +++ b/pulp_file/app/viewsets.py @@ -535,8 +535,6 @@ class FileDistributionViewSet(DistributionViewSet, RolesMixin): class FileAlternateContentSourceViewSet(AlternateContentSourceViewSet, RolesMixin): """ Alternate Content Source ViewSet for File - - ACS support is provided as a tech preview in pulp_file. """ endpoint_name = "file" diff --git a/pulp_file/docs/admin/guides/rbac.md b/pulp_file/docs/admin/guides/rbac.md index 946ba74f99..22ba7edbb6 100644 --- a/pulp_file/docs/admin/guides/rbac.md +++ b/pulp_file/docs/admin/guides/rbac.md @@ -15,10 +15,6 @@ This document describes the default access policies shipped with Pulp File. Each policies can be modified to achieve a different RBAC behavior. Use the Pulp CLI to follow along with the examples here. -!!! note - This feature is currently in tech preview and is subject to change in future releases. - - !!! note Customizing the access policy will cause any future changes to the default policies, like statement changes and bugfixes, to be ignored unless reset to the default policy. diff --git a/pulpcore/app/viewsets/access_policy.py b/pulpcore/app/viewsets/access_policy.py index 35b69a3e81..3c75827517 100644 --- a/pulpcore/app/viewsets/access_policy.py +++ b/pulpcore/app/viewsets/access_policy.py @@ -16,9 +16,6 @@ class AccessPolicyViewSet( ): """ ViewSet for AccessPolicy. - - NOTE: This API endpoint is in "tech preview" and subject to change - """ queryset = AccessPolicy.objects.all()