[DOCS-4836] 2.6 still "unstable" ? Created: 17/Feb/15 Updated: 16/Mar/15 Resolved: 17/Feb/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | production |
| Affects Version/s: | mongodb-2.6 |
| Fix Version/s: | v1.3.18 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Aaron Clements | Assignee: | Michael Paik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 1 day ago |
| Description |
|
Good morning! Can you give us some details about why 2.6 is still listed as unstable? We are getting ready to test upgrading in QA and stage, but I'm hesitant to bring it to Production because it's still listed as "unstable". Do you have many customers running this in Production? |
| Comments |
| Comment by Aaron Clements [ 17/Feb/15 ] |
|
Thank you for the clarification. This makes it a lot easier. |
| Comment by Michael Paik [ 17/Feb/15 ] |
|
Aaron, 2.6 has been the 'stable' release since April 2014, and many customers are running it. It is listed as the production release at the upper-left of the Downloads page. I believe you are looking at the 2.6 Nightly under the 'Unstable' releases, which are the ongoing day-to-day changes that eventually get rolled up into patch releases. |