IBM Cloud - Structured Ideas

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you.

  1. To post a new idea - select "Add a new idea" and where asked select the appropriate category this idea relates to. Provide requested information to allow us to get a better understanding of your request.

  2. Vote ideas that matter most to you.

  3. Get feedback from the IBM team to refine your idea.

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

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
  • Oct 17 2016
  • Not under consideration
  • Guest commented
    21 Nov, 2016 09:25pm

    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 commented
    21 Nov, 2016 03:36pm

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

  • Guest commented
    17 Oct, 2016 07:03pm

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

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.