Task #5563
Label things as tech-preview
0%
Description
There are a few areas of Pulp3 that are merged, but may have changes made to it in the future. The docs need to clearly indicate these at the top of those documentation sections.
Items¶
- S3 Support
- The django-admin
stage-profile-summarycommand - PROFILE_STAGES_API setting https://docs.pulpproject.org/en/3.0/nightly/installation/configuration.html#profile-stages-api
- Exporters
- The names of tasks, we know we're moving them some later.
Associated revisions
Revision 19ee3858
View on GitHub
Label file system exporter as a tech preview
ref #5563
Revision 330309ad
View on GitHub
Label file system exporter as a tech preview
ref #5563
(cherry picked from commit 19ee3858cc2f11b722e9966d7bb202bedbd5b91d)
Required PR: https://github.com/pulp/pulpcore/pull/450
Revision 4baeedb0
View on GitHub
Label things as tech preview
ref #5563
(cherry picked from commit 187bdfdedead6a79cc017d6de015c2f74f5ce970)
Required PR: https://github.com/pulp/pulp_file/pull/332
History
#1
Updated by bmbouter about 1 year ago
- Description updated (diff)
#2
Updated by daviddavis about 1 year ago
- Groomed changed from No to Yes
#3
Updated by daviddavis about 1 year ago
What about adding the Exporter code as well?
#4
Updated by bmbouter about 1 year ago
daviddavis wrote:
What about adding the Exporter code as well?
I personally don't think we need to label them because they are so straightforward, but you feel we should I'm ok w/ that.
#5
Updated by daviddavis about 1 year ago
- Tracker changed from Issue to Task
- % Done set to 0
#6
Updated by bmbouter about 1 year ago
- Description updated (diff)
#7
Updated by bmbouter almost 1 year ago
- Description updated (diff)
#8
Updated by daviddavis 12 months ago
Some of these things aren't in our docs. What if we have a tech preview list in our 3.0 announcement?
#9
Updated by bmbouter 12 months ago
daviddavis wrote:
Some of these things aren't in our docs. What if we have a tech preview list in our 3.0 announcement?
We probably should include this in the 3.0 announcement either way. I started that doc here: https://docs.google.com/document/d/1WC_ooHYuYlNGbGg9WOBW3Qbq9E7YAx1Bv1F2ZODOMFk/edit
We should add a section to the changelog also maybe?
What about adding labels to the docstrings so they show up in the swagger API docs?
#10
Updated by daviddavis 12 months ago
We should add a section to the changelog also maybe?
That sounds good.
What about adding labels to the docstrings so they show up in the swagger API docs?
If there's an easy way to do this (and it's easy to rollback once we release 3.1) then that sounds fine to me. I don't think there is though?
#11
Updated by daviddavis 12 months ago
Actually, Exporters are the only thing here that show up in the REST API. We could label those as tech preview in the docstring/swagger API I think.
#13
Updated by daviddavis 12 months ago
Opened a couple PRs:
https://github.com/pulp/pulp_file/pull/331
https://github.com/pulp/pulpcore/pull/448
#14
Updated by bmbouter 12 months ago
- Status changed from NEW to POST
- Assignee set to daviddavis
Final PR available as part of changelog for 3.0.0: https://github.com/pulp/pulpcore/pull/453
Please register to edit this issue
.
Label things as tech preview
ref #5563