Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-100

Publication Mechanism for Branched Releases

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • None
    • manual
    • None

    Description

      We need to be able to have a way to publish the new documentation so that we can maintain branches of the documentation for each release, so that users are not confused by feature changes in releases. The documentation will:

      • Have a "current," branch that will track ongoing development with MongoDB, and will be the main documentation.
      • Have branches for each release that are branched from current after each release, that will be maintained as long as the release is supported.

      All of these branches need to be able to be published at any time

      The apidocs repository does something very similar with a tag-based approach which won't support our ongoing maintenance requirements.

      Attachments

        Activity

          People

            sam.kleinman Sam Kleinman (Inactive)
            sam.kleinman Sam Kleinman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              12 years, 3 weeks ago