Uploaded image for project: 'JBoss Core Services'
  1. JBoss Core Services
  2. JBCS-1618

Prepare JBCS 2.4.57 product docs for publishing

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • httpd 2.4.57 GA
    • None
    • Documentation
    • None
    • JWS/JBCS Sprint 45

    Description

      This ticket covers the following tasks to prepare the 2.4.57 docs for publishing:

      • Create a 2.4.57 branch in Gitlab.
      • Create the following 2.4.57 doc titles in Pantheon:
        • Apache HTTP Server Installation Guide
        • Apache HTTP Server Connectors and Load Balancing Guide
        • Red Hat JBoss Core Services ModSecurity Guide
      • Add the following links to the 2.4.57 doc splash page in Pantheon:

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. JBCS-1597 Create and publish the Apache HTTP Server 2.4.57 Installation Guide

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBCS-1600 Create and publish 2.4.57 version of the HTTP Connectors and Load Balancing guide

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBCS-1601 Create and publish 2.4.57 version of the ModSecurity guide

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              rhn-support-khosford Kieran Hosford
              rhn-support-khosford Kieran Hosford
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: