[DOCS-100] Publication Mechanism for Branched Releases Created: 06/Jan/12  Updated: 30/Oct/23  Resolved: 01/Feb/12

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Sam Kleinman (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 12 years, 3 weeks ago

 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.



 Comments   
Comment by Sam Kleinman (Inactive) [ 01/Feb/12 ]

After meeting with Michael, we have the method for branched releases complete and in the repository.

Comment by Sam Kleinman (Inactive) [ 27/Jan/12 ]

I have a solution that works (uncommited/published at the moment) for this but I'll wait to close this until kbanker and miketheman have looked at and approved things.

Comment by Sam Kleinman (Inactive) [ 25/Jan/12 ]

Mike,

I'm assigning it to you so we can make sure that we're on the same page regarding how the new docs get published.

Cheers,
sam

Generated at Thu Feb 08 07:37:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.