control buildpack update frequency

Although the approximate 1 month buildpack updated frequency is appreciated by a large segment of our customers - there are a  number of enterprise customers which have longer application and maintenance cycles than 1 month.  What this means is that they are not able to spend the time each month to validate and/or fix regressions in their apps that may happen or to do any blue-green testing before going live with updates.  

We have several customers asking us to provide a way for them to control the upgrades of buildpacks ...or keep a longer number of older buildpacks around. They are looking at a 3 or 6 month buildpack upgrade cycle.