Permission Click Release Calendar, Communications, and Version Naming Convention Changes

[#1]

Dear Permission Click Customers,

The Permission Click team is implementing some impactful changes to release cadence, communications, and naming conventions we wanted you to be aware of.

We hope these changes provide you with a more reliable and stable experience and keep you better informed.

Release Calendar

We’re implementing a structured release calendar so that you can, in general, expect releases to occur as defined within this structure instead of the possibility of a release occurring any day.

Permission Click will deploy releases on the 1st and 3rd Thursdays of each month, but with some exceptions due to holidays.

However, if an urgent issue arises that requires immediate resolution, an impromptu escalation release may still occur, though additional scrutiny will be applied to determine the true need for an escalation release and the cost of delaying resolution until the next scheduled release.

In advance of each scheduled release, we’re implementing additional quality assurance practices to improve the quality of releases.

Release Communications

The structured release calendar allows us to more proactively communicate the content and deployment date of each scheduled release. You can expect the following communications for scheduled releases:

• Release Notes
• What: Communicating the content of a particular release
• When: ~1 week prior to the targeted release deployment date
• Release Announcement
• What: Communicating a release is targeted for a particular date, and linking to the release notes
• When: ~1 week prior to the targeted release deployment date
• Release Adjustment (only if a change to the targeted release deployment date is required)
• What: Communicating a change in the targeted release deployment date, and linking to the release notes
• When: As soon as a change is determined
• Release Notification
• What: Communicating that a release is now available, and linking to the release notes
• When: Release deployment date, after the release deployment

Given escalation releases are impromptu, there will not be the same communications in advance of the release deployment. You can expect the following communications for escalation releases:

• Release Notes
• What: Communicating the content of a particular release
• When: Release deployment date, after the release deployment
• Release Notification
• What: Communicating that a release is now available, and linking to the release notes
• When: Release deployment date, after the release deployment

All of these communications will be posted in the Product Updates space for the Permission Click product in PowerSchool Community. Be sure to subscribe to this space in order to receive notifications when these communications are posted.

Release Version Naming Convention

To align with the structure of the release calendar, and to align with the standard release version naming convention used by most PowerSchool products, Permission Click’s release version naming convention will change as follows:

• PC_YY.M.N.E
• PC is the product code for Permission Click
• YY indicates the year
• M indicates the month
• N indicates the index of the count of that scheduled release in the month
• E indicates whether the release is a scheduled release or an unscheduled escalation release, and the count of the index of that unscheduled release

Examples:

• PC_25.1.0.0 is the first scheduled release in Jan 2025
• PC_25.2.0.0 is the first scheduled release in Feb 2025
• PC_25.2.1.0 is the second scheduled release in Feb 2025
• PC_25.2.1.1 is the first unscheduled escalation release after the second scheduled release in Feb 2025
• PC_25.2.1.2 is the second unscheduled escalation release after the second scheduled release in Feb 2025

- Your Permission Click Team

Was this Article Helpful?

• Kudo this article if you found it helpful. It will help others find this resource.
• Comment directly on this article to request clarification or share feedback about the content of the article.
• Use the product-specific forum for questions not directly related to this article.

[#2]

Dear Permission Click Customers,

The Permission Click team is implementing some impactful changes to release cadence, communications, and naming conventions we wanted you to be aware of.

We hope these changes provide you with a more reliable and stable experience and keep you better informed.

Release Calendar

We’re implementing a structured release calendar so that you can, in general, expect releases to occur as defined within this structure instead of the possibility of a release occurring any day.

Permission Click will deploy releases on the 1st and 3rd Thursdays of each month, but with some exceptions due to holidays.

However, if an urgent issue arises that requires immediate resolution, an impromptu escalation release may still occur, though additional scrutiny will be applied to determine the true need for an escalation release and the cost of delaying resolution until the next scheduled release.

In advance of each scheduled release, we’re implementing additional quality assurance practices to improve the quality of releases.

Release Communications

The structured release calendar allows us to more proactively communicate the content and deployment date of each scheduled release. You can expect the following communications for scheduled releases:

• Release Notes
• What: Communicating the content of a particular release
• When: ~1 week prior to the targeted release deployment date
• Release Announcement
• What: Communicating a release is targeted for a particular date, and linking to the release notes
• When: ~1 week prior to the targeted release deployment date
• Release Adjustment (only if a change to the targeted release deployment date is required)
• What: Communicating a change in the targeted release deployment date, and linking to the release notes
• When: As soon as a change is determined
• Release Notification
• What: Communicating that a release is now available, and linking to the release notes
• When: Release deployment date, after the release deployment

Given escalation releases are impromptu, there will not be the same communications in advance of the release deployment. You can expect the following communications for escalation releases:

• Release Notes
• What: Communicating the content of a particular release
• When: Release deployment date, after the release deployment
• Release Notification
• What: Communicating that a release is now available, and linking to the release notes
• When: Release deployment date, after the release deployment

All of these communications will be posted in the Product Updates space for the Permission Click product in PowerSchool Community. Be sure to subscribe to this space in order to receive notifications when these communications are posted.

Release Version Naming Convention

To align with the structure of the release calendar, and to align with the standard release version naming convention used by most PowerSchool products, Permission Click’s release version naming convention will change as follows:

• PC_YY.M.N.E
• PC is the product code for Permission Click
• YY indicates the year
• M indicates the month
• N indicates the index of the count of that scheduled release in the month
• E indicates whether the release is a scheduled release or an unscheduled escalation release, and the count of the index of that unscheduled release

Examples:

• PC_25.1.0.0 is the first scheduled release in Jan 2025
• PC_25.2.0.0 is the first scheduled release in Feb 2025
• PC_25.2.1.0 is the second scheduled release in Feb 2025
• PC_25.2.1.1 is the first unscheduled escalation release after the second scheduled release in Feb 2025
• PC_25.2.1.2 is the second unscheduled escalation release after the second scheduled release in Feb 2025

- Your Permission Click Team

Was this Article Helpful?

• Kudo this article if you found it helpful. It will help others find this resource.
• Comment directly on this article to request clarification or share feedback about the content of the article.
• Use the product-specific forum for questions not directly related to this article.

[#3]

Dear Permission Click Customers,

The Permission Click team is implementing some impactful changes to release cadence, communications, and naming conventions we wanted you to be aware of.

We hope these changes provide you with a more reliable and stable experience and keep you better informed.

Release Calendar

We’re implementing a structured release calendar so that you can, in general, expect releases to occur as defined within this structure instead of the possibility of a release occurring any day.

Permission Click will deploy releases on the 1st and 3rd Thursdays of each month, but with some exceptions due to holidays.

However, if an urgent issue arises that requires immediate resolution, an impromptu escalation release may still occur, though additional scrutiny will be applied to determine the true need for an escalation release and the cost of delaying resolution until the next scheduled release.

In advance of each scheduled release, we’re implementing additional quality assurance practices to improve the quality of releases.

Release Communications

The structured release calendar allows us to more proactively communicate the content and deployment date of each scheduled release. You can expect the following communications for scheduled releases:

• Release Notes
• What: Communicating the content of a particular release
• When: ~1 week prior to the targeted release deployment date
• Release Announcement
• What: Communicating a release is targeted for a particular date, and linking to the release notes
• When: ~1 week prior to the targeted release deployment date
• Release Adjustment (only if a change to the targeted release deployment date is required)
• What: Communicating a change in the targeted release deployment date, and linking to the release notes
• When: As soon as a change is determined
• Release Notification
• What: Communicating that a release is now available, and linking to the release notes
• When: Release deployment date, after the release deployment

Given escalation releases are impromptu, there will not be the same communications in advance of the release deployment. You can expect the following communications for escalation releases:

• Release Notes
• What: Communicating the content of a particular release
• When: Release deployment date, after the release deployment
• Release Notification
• What: Communicating that a release is now available, and linking to the release notes
• When: Release deployment date, after the release deployment

All of these communications will be posted in the Product Updates space for the Permission Click product in PowerSchool Community. Be sure to subscribe to this space in order to receive notifications when these communications are posted.

Release Version Naming Convention

To align with the structure of the release calendar, and to align with the standard release version naming convention used by most PowerSchool products, Permission Click’s release version naming convention will change as follows:

• PC_YY.M.N.E
• PC is the product code for Permission Click
• YY indicates the year
• M indicates the month
• N indicates the index of the count of that scheduled release in the month
• E indicates whether the release is a scheduled release or an unscheduled escalation release, and the count of the index of that unscheduled release

Examples:

• PC_25.1.0.0 is the first scheduled release in Jan 2025
• PC_25.2.0.0 is the first scheduled release in Feb 2025
• PC_25.2.1.0 is the second scheduled release in Feb 2025
• PC_25.2.1.1 is the first unscheduled escalation release after the second scheduled release in Feb 2025
• PC_25.2.1.2 is the second unscheduled escalation release after the second scheduled release in Feb 2025

- Your Permission Click Team

Was this Article Helpful?

• Kudo this article if you found it helpful. It will help others find this resource.
• Comment directly on this article to request clarification or share feedback about the content of the article.
• Use the product-specific forum for questions not directly related to this article.