FAQ
      Back to home
      1. Feature Knowledge Base
      2. MSR | Mysolution Recruitment
      3. FAQ

      All About Feature Updates, Quality Updates, and Hotfixes

      We regularly receive questions about how our release process works. To provide clarity, we’ve created a clear overview of the different types of releases and how they are rolled out.

      Below, you can read what to expect with a new Release, Quality Update, or Hotfix and how the rollout process works.

      Feature Update

      What is it?
      Major technical or functional changes, such as modifications to components, new layouts, or updates to comply with new legislation (compliance). These updates also include all improvements from previous Quality Updates and Hotfixes.

      • Testing period: 2 to 4 weeks
      • Frequency:
        • 3 times per year for MSR and MSF
        • 12 times per year for MSW
        • Planned and documented in: 🔗 the release schedule
      • Examples: New functionalities, enhanced reporting capabilities, or adjustments to meet new legal requirements.

      Quality Update

      What is it?
      Maintenance updates including bug fixes, performance improvements, and occasionally small adjustments for new regulations.

      • Testing period: 5 days
      • Frequency:
        • 6 times per year for MSR and MSF
        • MSW currently does not receive Quality Updates
        • Planned and documented in: 🔗 the release schedule
      • Examples: Bug fixes, improvements to existing features, or adding minor updates.

      Hotfix

      What is it?
      A solution for an urgent production issue that needs to be resolved quickly. These updates do not contain new functionalities.

      • Frequency: Not planned, carried out ad hoc
      • Examples: Critical bug fixes that directly affect your production environment.

      The Rollout Process

      Phased Rollout of Feature Updates

      Our feature updates are rolled out in multiple phases. This ensures a smooth transition and helps minimize potential issues.

      • Step 1: Testing and Preparation (Week 1)

        • The new features are thoroughly tested in a simulated production environment.
        • On Monday afternoon, the updates are installed in the MSF test environment.
        • You receive installation links for the MSR and Combi packages.

      • Step 2: Gradual Introduction into Production (Weeks 3–5)

        • Week 3, Monday evening: Phase 1 installation for MSF and MSR/Combi in production.
        • Week 4, Friday evening: Phase 2 installation for MSF and MSR/Combi in production.
        • Week 5, Friday evening: Phase 3 installation for MSF and MSR/Combi in production.

      Clustering

      What does it involve?
      You are grouped into a cluster based on your MSF cloud. Customers using only MSR are evenly distributed across the clusters.

      • Why clustering?
        This approach allows us to closely monitor the impact of updates, especially during the first two phases.

      • Even distribution:
        Each cluster has approximately the same number of customers. Each cluster follows a different phase schedule, ensuring you’re not always in the same phase.

      • Fixed clusters:
        Once assigned, you remain in the same cluster to keep the process consistent.

      Managing MSR and Combi Package Updates in Sandboxes

      You can decide when and on which sandboxes to install updates during the testing period of a Feature Update or Quality Update.

      • How does it work?
        • Use the special installation link available in Topdesk under the “MSR Releases” tile.
        • You will receive a notification as soon as an update becomes available.
      • Benefits:
        More flexibility and control over your testing environment.

      Production Environment

      • Updates in the production environment will continue to be handled by us, following the release schedule.
      • We always use the latest version of the software.

      Questions?

      If you have any questions about the rollout schedule or cluster assignment, don’t hesitate to contact your Customer Success Manager.