-
Type: Epic
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Summary
Outline a roadmap to move all drivers to evergreen-based-releases.
Motivation
Drivers releases are often downloaded from package index (pip, maven, cpan) or from github directly. Currently only some of the driver releases are signed and the process of signing them is not standardized. Releasing drivers via Evergreen will allow us to better audit the release process (including signing packages). For many of our customers there is a requirement to adhere to an SDLC process that ensures the packages we provide are not tampered with by any internal participant in the process of producing and releasing those packages. Often these requirements are stated by our customers in security and compliance questionnaires. Currently, we list exceptions on these questionnaires related to drivers SDLC and signed packages. This effort should reduce the friction during sales cycles due to the number of exceptions we list.
Cast of Characters
Document Author: Rathi Gnanasekaran
Product Owner: Rachelle Palmer
Program Manager: Alexander Golin & Esha Bhargava
Stakeholders: Drivers
Documentation
- depends on
-
CDRIVER-2845 Improve C driver release process
- Development Complete
-
CXX-1676 Automate C++ driver release process
- Development Complete
-
PHPLIB-583 Automate PHPLIB Release Process
- Development Complete
-
NODE-5222 Use GitHub triggers for Node driver release
- Closed
-
NODE-6115 Sign release artifacts or tags with MongoDB-managed keys
- Closed
-
CSHARP-3200 Release on Evergreen
- Closed
-
CXX-2100 Automate Driver Releases
- Closed
-
GODRIVER-1737 Automate Driver Releases
- Closed
-
JAVA-3793 Support publishing release builds on Evergreen
- Closed
-
JAVA-3827 Automate Driver Releases
- Closed
-
MOTOR-616 Automate Driver Releases
- Closed
-
NODE-2792 Automate Driver Releases
- Closed
-
PHPC-1674 Automate Driver Releases
- Closed
-
RUBY-2390 Automate Driver Releases
- Closed
-
RUST-546 Automate Driver Releases
- Closed