| Table of Contents |
|---|
...
In some cases, typically when a substantial change is included in a major release, the entire version may increment, e.g., from 3.2 to 4.0.
- Sarah Holst Do you know how the Major Release Cycle grid was created and where we can update it?
...
Hotfix Release Process/Typical Timeline
...
Emergency releases are used only for issues that meet the P1 definition as outlined in the https://hub.aspenware.net/main/Aspenware-Service-Explained.1722253405.html.
Jen Dixon should we say something in here about how hotfixes may or may not have release notes associated with them?
Overall Installation/Update Process
...
For scheduled releases, the following process will be followed for Aspenware to certify that a release is completed.
Steps in blue are the responsibility of the customer.
Release Pre-work
Timing: 3 - 7 Days before the scheduled release
Aspenware will send out a notice of the new release along with release notes and configuration guides for production-impacting changes. Customers can elect to take the version to their test environment.
Upon electing to take the release to your test environment, Aspenware will deploy the version to your test site, smoke test it internally, and then send the smoke test checklist to be completed by the resort.
When the resort has completed the checklist and feels comfortable with the release, they will contact their Aspenware Representative, signing off on the release.
Once accepted, Aspenware will work with the resort to schedule the release. They will select an available release date using Calendly, which will send a calendar invite for the time of the release. To invite additional customer representatives (defined above), they will need to include their emails in your Calendly request.
It is expected during this scheduled time that all invited representatives, especially the primary contact and accounting representative, are available to answer emails and complete checks requested of them quickly. If they are not available, it is their responsibility to notify Aspenware of their absence so a new time can be scheduled, or a backup can be found.
If the release requires configuration updates in Aspenware Commerce or Unity between the time of the release of the code and the re-enablement of the site, Aspenware will work with the customer representatives (defined above) to train the contacts on the required configuration and to compile a complete go-live configuration checklist to be completed by Aspenware, and/or some tasks by the resort main contact during the downtime. These configurations will be done from the staging environment by Aspenware and/or the customer representatives (defined above).
...
If deemed necessary by Aspenware, about 1 hr before the scheduled release, Aspenware will take a backup of the current site’s database. Depending on the size of the shop’s database, this may take between 10 min to 2 hrs.
Note: Any orders placed between the time the backup is started and the site is taken down with the maintenance page will not be included in the restored site if for any reason, the deployment is aborted and the backup DB needs to be restored to production.
If the backup takes longer than expected, or if another factor is delaying the deployment of code, Aspenware will email the group of customer representatives (defined above) to re-assess and plan a different time.
If a release requires downtime, once the backup is taken, the site is will be taken offline. When the site is taken down, a maintenance page will be displayed for the entirety of the release. Aspenware will email all customer representatives (defined above) to confirm that the deployment is starting and the site will be taken down.
When the site is down, the new code will be deployed to a staging slot. Once the code deployment is complete to the staging slot, the developer doing the deployment provides a URL to the staging page to the responsible Aspenware Representative. It is the Aspenware Representative’s responsibility to check the site.
When the staging URL is ready, the Aspenware Representative will step through the go-live certification checklists. Every step on these checklists must be completed before confirming that the production site can be re-deployed and the maintenance page may be removed. The site will not be turned from maintenance mode to live mode unless every step is completed in the checklists successfully, or unless the customer representatives (defined above) give explicit instructions to turn the site back on despite checks not being completed.
The following checks are required and a part of this go-live certification checklist.
Create a new customer and family memeber and confirm that it loads in the resort’s production POS with expected information (email, alternate id, name, dob, authentication profile)
Checkout with an order using a real credit card
Confirm that the order is in production POS under the correct person and for the correct dollar amount.
Email Accounting contact (defined above) to confirm that transaction is inthe customer’s payment provider for the correct amount.
Aspenware will email the Order ID, order total, name of customer ordering product, name of cardholder, last 4 of cc, and expiration date.
The accounting representative (defined above), or someone with access to the payment provider at the resort is responsible for quickly checking the transaction and emailing Aspenware to confirm or deny that the transaction made it in. The customer is also responsible for refunding these test production transactions in the payment provider and/or the POS.
If the transaction is successful, the customer contact should immediately refund the transaction in the POS.
Logout and log back in with an existing customer
Confirm that the email is successfully delivered
Check store settings in admin to confirm that the correct URL is added and the ‘/’ is present after the URL.
Confirm that site is SSL.
Click through products and categories on the store to confirm that everything appears to render correctly.
The Aspenware representative will then complete the upgrade checklist that is unique to the code being deployed and is made the prior week by the Client Services Manager and Release Manager.
If any of these checks are not able to be completed in a timely manner, especially the accounting check task above, Aspenware will follow up with the primary contact (defined above) to have them follow up with the required parties.
If any of these checks are not able to be completed in a timely manner, especially the accounting check task above and the primary contact is not able to be reached, Aspenware will follow up with the secondary contact (defined above) to have them follow up with required parties.
If the uncompleted check can still not be verified after reasonable efforts have been made to reach out, the primary or secondary contact (defined above) only can give permission to Aspenware to flip the site back on despite certain go-live certification checklist items remaining incomplete. The site will not be turned from maintenance mode to live mode unless every step is completed in the checklist successfully, or unless the customer representative (defined above) gives explicit instructions to turn the site back on despite checks not being completed.
If the site is flipped back on without key tasks being completed, within 24 hours following the flip back, Aspenware and the primary contact should attempt to re-contact those responsible for outstanding tasks.
Once all tasks are completed, Aspenware will email the group of customer representatives (defined above) declaring that the site is Certified by Aspenware and complete.
...
For unscheduled emergency releases, such as P1 site outages, which are not planned in advance, the following process will be followed for Aspenware to certify that a release is completed.
Steps in blue are the responsibility of the customer.
Day-of Release Activities
Aspenware will reach out to the resort to get permission before beginning release activities to fix a P1 issue.
The customer will grant permission before Aspenware begins.
If possible and deemed necessary, Aspenware will take a backup of the current site’s commerce database. Depending on the size of the shop’s database, this may take between 10 min to 2 hrs.
Note: Any orders placed between the time the backup is started and the site is taken down with the maintenance page will not be included in the restored site if for some reason, the deployment is aborted and the backup DB needs to be restored.
If the backup takes longer than expected, or if another factor is delaying the deployment, Aspenware will email the group of customer representatives (defined above) to re-assess and plan a later or different time.
If a release requires downtime, once the backup is taken, the site will taken offline. When the site is taken down, the maintenance page will be displayed for the entirety of the release. Aspenware will email all customer representatives (defined above) to confirm that the deployment is starting and the site will be taken down.
When the site is down, the new code will be deployed to a staging slot. Once the code deployment is complete to the staging slot, the developer doing the deployment provides a URL to the staging page to the responsible Aspenware Service Representative.
When the staging URL is ready, the Aspenware Representative will step through the go-live certification checklist. Every step on this checklist must be completed before confirming that the site can be re-deployed and the maintenance page removed. The site will not be turned from maintenance mode to live mode unless every step is completed in the checklist successfully, or unless the RESORT representative (defined above) gives explicit instructions to turn the site back on despite checks not being completed.
The following checks are required and a part of this go-live certification checklist.
Create a new customer and confirm that it loads in production RTP with expected information (email, alternate id, name, dob, authentication profile)
Checkout with an order using a real Credit Card - Payeezy and Square payments cannot be completed from a stage URL, so this step can only be done from the production store for those payment providers.
Confirm that order is in production RTP under the correct person and for the correct dollar amount
Email Accounting contact to confirm that transaction is inthe customer’s payment provider for the correct $ amount.
Aspenware will email Order ID, order total, name of customer ordering product, name of cardholder, last 4 of cc, and expiration date.
The accounting representative (defined above), or someone with access to the payment provider at the RESORT is responsible for quickly checking the transaction(s) and emailing Aspenware to confirm or deny that the transaction made it in.
If the transaction is successful, they should immediately refund the transaction in the POS and/or payment gateway.
Logout and log back in with an existing customer
Confirm that email is successfully delivered
Check store settings in Nopcommerce admin to confirm that the correct URL is added and the / is present after the URL.
Confirm that site is SSL.
Click through products and categories on the store to confirm that everything appears to render correctly.
The Aspenware representative will then complete the upgrade checklist that is unique to the code being deployed and is made the prior week by the Client Services Manager and Release Manager.
If any of these checks are not able to be completed in a timely manner, especially the accounting check task above, Aspenware will follow up with the primary contact (defined above) to have them follow up with the required parties.
If any of these checks are not able to be completed in a timely manner, especially the accounting check task above and the primary contact is not able to be reached, Aspenware will follow up with the secondary contact (defined above) to have them follow up with required parties.
If the uncompleted check can still not be verified after reasonable efforts have been made to reach out, the primary or secondary contacts (defined above) only can give permission to Aspenware to flip the site back on despite certain go-live certification checklist items remaining incomplete. The site will not be turned from maintenance mode to live mode unless every step is completed in the checklist successfully, or unless the customer representative (defined above) gives explicit instructions to turn the site back on despite checks not being completed.
If the site is flipped back on without key tasks being completed, within 24 hours following the flip back, Aspenware and the primary contact should attempt to re-contact those responsible for outstanding tasks.
Once all tasks are completed, Aspenware will email the group of RESORT representatives (defined above) declaring that the site is Certified by Aspenware and complete.
...
*Unfinalized code: has been tested by Aspenware, but is not the final release version.
Beta Testing Expectations
...
Read all available release notes specific to the release.
Actively test all product types currently available on your site before the beta testing window closes.
Promptly report any issues that arise with the following information:
Description of the problem.
Detailed steps to recreate the issue, including specific products, quantities, and product dates to use.
Screenshots of errors presented on screens, or the outcome of the error condition (e.g., point of sale order discrepancies).
...