Non-availability of upgrade pricing from ColdFusion 10 to ColdFusion (2016 release)

As you may be aware, core support for ColdFusion 10 will end on the 16th of May, 2017. 

This post is to give you a heads-up that post 31st May 2017, the upgrade pricing to upgrade from ColdFusion 10 to ColdFusion (2016 release) will no longer be available. You must pay the full price to procure licenses for ColdFusion (2016 release) if you only have licenses for ColdFusion 10 or below, post 31st May 2017. 

Please note that if you are already subscribed to a Maintenance and Support (M&S) Plan or an Upgrade Plan you already would have access to the latest version and will continue to have access to the latest version till you are subscribed, irrespective of the version of ColdFusion that you are running on production. For instance, you may still be on ColdFusion 10 in production, but are already under an M&S Plan. In this scenario, you have access to the latest version anyway and this has no direct relevance to you even after 31st May 2017.

 

Adobe ColdFusion survey – 2016

This post is to announce a new survey titled the Adobe ColdFusion survey – 2016. I request you to take time to provide your valuable feedback via the survey.

The results of the survey will help us validate certain hypothesis we have to build the future versions of the product. We are already in the process of planning for the next version of ColdFusion, codenamed Aether.

Here is the survey link again. Part of the survey result will also be presented at Adobe ColdFusion Summit this year. Thank you for your time.

 

Bug fixes in ColdFusion (2016 release)

We acknowledged at CFSummit that we need to move the needle when it comes to bug fixes in the product. Just as we had announced, we are making improvements in this axis.

Here are some of the highlights so far.

A total of 423 legacy bugs (legacy bugs are those that were reported in previous versions starting from ColdFusion 11) were resolved as a part of the release.

A total of 95 external bugs were fixed in just update 1 and update 2 for ColdFusion 2016. More details about what fixes went in update 2 can be found in this post.

The average age for bugs to be verified by the product team from the time it is logged in the system is now down to 4 days. This was around 35 days during the ColdFusion 11 timeframe. This gives you a good sense of comparison between where we were and where we are headed towards.

Also, the upcoming update 3 promises to be an even significant update in terms of bug fixes when compared to update 1 and update 2. Stay tuned to hear about the upcoming update. 

I want to leave you with the message that we are monitoring our improvements in this space very closely. You will hear more details about our overall improvements to bug fixes at CFSummit this year. We look forward to seeing you there!

 

Adobe ColdFusion survey for the next version

As you are probably aware, we are in the planning stage for the next version of ColdFusion. You may have already seen a blog post asking you to submit your wishlist for the next version.

This post is about a survey that will give Adobe valuable information about your usage of ColdFusion. Please take a few minutes to take this survey and provide your feedback. The data from the survey will be used to validate a set of hypothesis about the usage of ColdFusion. This will eventually help us build a great next version of ColdFusion, codenamed Aether.

Thank you for your valuable time. Here is the survey link again.

 

 

 

 

ColdFusion (2016 release) – Security audit report

As you are probably aware, with each version of ColdFusion, security is at the top of the priority list. With the latest release of ColdFusion, it is not just the security related features. Emphasis was laid on the inherent security of the ColdFusion platform by itself. To validate this, the PSIRT (Product Security Incident Response Team) at Adobe helped arrange a third party security audit for ColdFusion. The audit did come up with a few findings. Our Product engineers did an excellent job of mitigating all the findings to the fullest. 

To validate the above claim, we now have a public facing security report, from the agency that performed the security audit, indicating that 100% of all findings have been mitigated. Here is the public facing report with all the details. You can also view the link to this security audit report under datasheets and whitepapers section of the ColdFusion product home page on the Adobe website.

Submitting your wishlist for the next version of ColdFusion

Here is a way to let us know your wishlist for the future versions of ColdFusion. The process is really simple.

 

1. Log into the public bug tracker https://bugbase.adobe.com

2. Click on Add Bug. 

3. Choose ColdFusion as the product and version as 2016. Remember, the version to be selected is 2016.

4. Select product area as wishlist and submit your list in the bug description.

 

That’s it! We would love to hear your thoughts on what you would like to see as a part of upcoming versions.

 

 

Installers for ColdFusion (2016 release) and ColdFusion Builder (2016 release) refreshed

The installers for ColdFusion (2016 release) and ColdFusion Builder (2016 release) have been refreshed. The only change between the old and new installers is the refresh of certain branding assets (no change in the underlying code). 

The new build number for ColdFusion (2016 release) is 298074 (was 297996 earlier) and for ColdFusion Builder (2016 release) is 298077 (was 298004 earlier). Some, if not all, branding assets refresh will also be fixed as a part of the first update so that users on previous installation get the latest branding assets.