Project

Profile

Help

Task #5563

Label things as tech-preview

Added by bmbouter about 2 months ago. Updated 2 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
No
Tags:
Documentation
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

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

History

#1 Updated by bmbouter about 2 months ago

  • Description updated (diff)

#2 Updated by daviddavis about 2 months ago

  • Groomed changed from No to Yes

#3 Updated by daviddavis about 2 months ago

What about adding the Exporter code as well?

#4 Updated by bmbouter about 2 months 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 2 months ago

  • Tracker changed from Issue to Task
  • % Done set to 0

#6 Updated by bmbouter about 1 month ago

  • Description updated (diff)

#7 Updated by bmbouter 13 days ago

  • Description updated (diff)

#8 Updated by daviddavis 2 days 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 2 days 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?

Please register to edit this issue

Also available in: Atom PDF