If you are attending R/Pharma 2025, you probably enjoy actively contributing to open source R packages for the pharma industry. Fixing bugs, implementing new features and expanding the use-case is work that feels motivating and meaningful. However, what happens if/when your package reaches a point of stability and maturity, where the main use-case is answered and feature completeness is in sight? How can you sustain your development team's momentum without chasing perfection, in a time where the active workload is naturally diminished? What should your new priorities be?

While there is no definitive answer to any of these questions, this talk will discuss the evolution of packages like {admiral} as they transition from active development to mature maintenance, drawing insights from the {admiral} team's experiences in navigating this complex shift.
Edoardo Mancini
Roche
R we there yet? {admiral}’s journey transitioning from active development to stability
If you are attending R/Pharma 2025, you probably enjoy actively contributing to open source R packages for the pharma industry. Fixing bugs, implementing new features and expanding the use-case is work that feels motivating and meaningful. However, what happens if/when your package reaches a point of stability and maturity, where the main use-case is answered and feature completeness is in sight? How can you sustain your development team's momentum without chasing perfection, in a time where the active workload is naturally diminished? What should your new priorities be?  While there is no definitive answer to any of these questions, this talk will discuss the evolution of packages like  admiral  as they transition from active development to mature maintenance, drawing insights from the  admiral  team's experiences in navigating this complex shift.