[SERVER-41630] Mongo Patch Policy Created: 11/Jun/19 Updated: 11/Jun/19 Resolved: 11/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.12, 3.6.13 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Ender Koca | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hello, How often security patches released ? Could we apply it automatically ? We used mongo db enterprise 3.6.12. My actual question is that how should be the patch policy including applying method(manual,auto), period ? How and where could we subscribe critical patches? |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 11/Jun/19 ] |
|
We do not release security patches in their own release; any changes will be provided in the form of a maintenance version (3.6.12 to 3.6.13 for example). Our documentation lists instructions on how to install various versions of MongoDB. If you would like us to automatically update your database for you, please see our Atlas product. Please note, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to a bug, I will now close it. If you need further assistance or recommendations as to how users update their environments, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. |
| Comment by Ender Koca [ 11/Jun/19 ] |
|
Could you send to information mail to burak.turkel@isbank.com.tr |