Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-2531

[toolchain] Jupiter Readiness effort

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • OSSM 2.0.0, OSSM 2.1.0
    • Documentation
    • None
    • [toolchain] Jupiter Readiness effort
    • False
    • False
    • 100
    • 100% 100%

      Go through the Jupiter Readiness Checklist and prepare both the Service Mesh and distributed tracing files for the new publication pipeline.

      https://docs.engineering.redhat.com/pages/viewpage.action?spaceKey=JUP&title=Jupiter+Source+files+readiness+Checklist

       

      Things we already know need to be done:

      • Add content type attributes.  Some of this will be automated by the OpenShift team, but there will be manual cleanup involved.
      • Some sort of change to the document attributes files.  The Service Mesh team adopted document attributes before the OpenShift team did, so there are two separate files for OSSM and DT.  In order to simplify things for Jupiter these files may be moved to a different folder (and all includes will need to be updated) and/or our two separate files will be merged into the OpenShift common-attributes.adoc file (which would still required updating the includes).

       

            Unassigned Unassigned
            jstickler Julie Stickler (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: