[DOCS-10798] Configure multiple versions for PHPLIB documentation Created: 15/Sep/17  Updated: 29/Oct/23  Resolved: 15/Sep/17

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

Type: Task Priority: Major - P3
Reporter: Jeremy Mikola Assignee: Andrew Aldridge
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to PHPLIB-284 Highlight API changes in documentation Closed
Participants:
Days since reply: 6 years, 21 weeks, 5 days ago
Story Points: 0.5

 Description   

PHPLIB's 1.2.0 release is coming soon, and we'd like to get our versioned documentation in order. At present, it looks like "1.1 (current)" is actually building from our master branch, which is actually 1.2-dev. This may be misleading our users into thinking that certain 1.2.0 APIs exist in 1.1.x, when they do not.

Ideally, we like to have the following:

  • "1.1 (current)" should build from v1.1
  • "1.2 (upcoming)" should build from master

Once 1.2.0 is released, I'll create a new ticket to have "1.2 (current)" be our default and have it build from v1.2. We can then add "1.3 (upcoming)", which will build from master. I believe this will closely resemble what the MongoDB manual does today.


Generated at Thu Feb 08 08:01:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.