This guide gives you an introduction to how to handle the release and migration of your extensions. It also briefly informs about Core’s release process.

Core's release schedule

We have two releases per year: one in May and one in November.

• Core Freeze 8 weeks before release
• Release candidate (RC0) is built 4 weeks before release

More details about our release process can be found here: CET Release Timelines

When should I migrate?

We recommend everyone to start migrating when Core reaches core freeze which is 8 weeks before the release. It would be great if the migration is completed about two weeks after Core freeze. When you have completed your migration, please build your extension and upload it to Core’s beta/RC boxes. There should be information about the beta and RC boxes in the developer briefcase. If you have any questions, please feel free to contact our developer support.

If you perform the migration early, you will be able to detect the issues earlier which will give your team more time to resolve the issues. Issues related to Core discovered earlier will give us time to fix those issues. So, migrating in good time means a more robust release, which results in happier users, happier managers and happier programmers!

What testing should be done?

Standard Level

1. Exploratory Test
   Perform exploratory test based on changes done during the migration. You can refer to Migration Testing Guides or ask your developers. Do note, perform this test only after you have finished migrating.
   
   
2. Standard Smoke Test
   Perform the smoke test after completing the exploratory test for the area's of focus.
   
   
3. Smoke Test for your extension
   Perform the smoke test on your extension after completing the standard smoke test. Ensure all existing features still work as intended.
   
   
4. Functional Test
   Perform the functional test for any new features in your extension and ensure all new features are working as intended.
   Preferably, these tests(step 1-4) should have been done already when Core reach feature freeze. If not, it’s time to do these tests now.

Advanced Level

1. Exploratory Testing
   Perform exploratory test based on changes done during the migration. You can refer to Migration Testing Guides or ask your developers. Do note, perform this test only after you have finished migrating.
   
   
2. Advanced Smoke Test
   Perform the smoke test after completing the exploratory test for the area's of focus.
   
   
3. Regression Test for your extension
   Perform the regression test on your extension after completing the advanced smoke test. Ensure all existing features still work as intended.
   
   
4. Functional Test
   Perform the functional test for any new features in your extension and ensure all new features are working as intended.
   
   Preferably, these tests(step 1-4) should have been done already when Core reach feature freeze. If not, it’s time to do these tests now.
5. Auto Test
   Have a machine to continuously run AutoTest which is found in CET Operator.

Release checklist - make sure you have done all these before release

• The extension has been tested (see section about testing above).
• Version numbers has been updated.
• The migration is completed (follow all steps in all sections in the migration guide).
• The extension is built and published to Core’s beta/RC boxes. Ensure your extension is published to the RC boxes.
• You have contacted the developer support if you have any questions.
• If you have release notes for your extension ensure it is written.
• If your extension supports multiple languages ensure all new resources has been translated.
• Any extension specific tasks should be completed.