Skip to Main Content
IBM Cloud - Structured Ideas

This portal is to open public enhancement requests against IBM Cloud and its products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

IBM Cloud Support Center ( – Use this site for any IBM Cloud defect or support need.

Stack Overflow ( – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud". - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Oct 17, 2016

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. 

  • Guest
    Nov 21, 2016

    It would be really useful if the default buildpacks (liberty-for-java) had version # associated to it. We only do this for older buildpacks. Once I choose the current buildpack with the version, I would expect it to be there for 6 months.

  • Guest
    Nov 21, 2016

    I'll comment just to re-inforce my +1 vote !!!

  • Guest
    Oct 17, 2016

    Thanks for the idea Fred. I've assigned this idea and tagged appropriately.