What is Continuous Delivery?
Continuous Delivery is a Software Engineering method that encourages more releases that come more often and correspondingly have a shorter time period between releases. Possible advantages are new features can be added and released as they are developed And defect fixes can be released sooner. In traditional approaches often defects were waiting for some new improvement to be finalized because everything was to be released in one large release. Continuous Delivery hopes to shorten the time from defect discovery to a release that resolves it.
Daeja ViewONE is using Continuous Delivery
Upgrades do not change the existing API functions. New releases may add functions or capabilities but an upgrade should not affect the applications that are using the package. Daeja ViewONE is a good candidate for the Continuous Delivery model.
Daeja Upgrades are simple, fast and certain
The actual upgrade method for Daeja ViewONE is to back up the current package and then expand and install the new software. Total time following the install instructions is measured in minutes not hours. This is one of the quickest and easiest upgrades we know of. Obviously this is a system upgrade and needs the professional care that a System Admin will give it. But it should be done easily and with minimal impact to the users.
How Developers view release levels
A note about the developers. They are working on the next release. A few of them or as a part time activity are looking at the previous release if there is a defect involved. They need to keep multiple source codes and testing systems around . We really want them working on the next release and keeping their focus there helps improve the quality of the product. Asking them to go back a revision is not very productive in the long run. What we think of as the current most up to date release is old news to them. They developed and tested it months ago. Their minds are on the next release. So if we ask them investigate the release before the current release that is actually two level back from where they are currently developing. It looks so old and in some ways unfamiliar. And if they see the defect they then need to look in newer code sets to see if it is there. It is unlikely that we would go backwards and make a special release for older code revision levels.
Continuous Deliver may resolve defects quickly
Daeja clients should consider the reality of this situation. If a defect is found then the first thing you may be asked to do is to upgrade to the current release. We have seen that most customers are already doing this and have been happy with the results. The reason is the defect may have been discovered previous to the current release and is resolved in the current release. If the defect goes away with an upgrade that is a good outcome for everyone. If the defect is still there then we can report it to the developers to investigate. And if we report it on the current release early enough in the cycle the fix might make it into the next release.
Two levels but really you want to be on the current one
IBM Software Support Policy is to support clients who are on the current release or the previous release levels. However, as we can see in this situation staying on the N-1 release is not going to be very productive. If you have the current (N) release then your responses to questions and support will be more a tune with the developers if they are needed. Being on the N-1 release level should be a clear indication that you need to upgrade to the current N level release. Reality is that some defects can be resolved by going up to the current release level. So if you call in with a problem a common response from support may be to upgrade
Quarterly appears to be the pattern
At this time Daeja appears to be releasing on a quarterly basis unless the size and complexity of a new feature puses the schedule. The Daeja team cannot 'commit' to this schedule but it sure looks like a pattern. Updates could almost be scheduled based on this schedule assuming you are willing to be flexible is something happens to offset the schedule. So you could wait a few weeks and then upgrade. So this could be done on a long-term scheduling process for your site.
You are not alone in your usage of Daeja ViewONE. There are many other users and support people working to make this product and your usage a success. Subscribing to the IBM My Notifications service is a critical first step. You should enroll with all your IBM Products, both hardware and software. This way you will receive "How to" documents along with other technical documents specific to your products. And you should also enroll in ECM Social Media channels for your products as well.
Daeja ViewONE is now using Continuous Delivery software methodology to deliver periodic upgrades. Upgrades are easy and straightforward to preform with few complications or risk. If IBM continues with this method, you could schedule site upgrades well in advance. Keeping up to date will deliver the best service from IBM Software Support.