# release cadence Published articles for release cadence. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## WebView2 is moving to a 2-week release cadence DevFeed: [WebView2 is moving to a 2-week release cadence]() Original publisher: [Read original article]() Author: Microsoft Edge Team Published: 2026-08-24T15:55:41Z Content type: release Language: en Sources: [Microsoft Edge Blog]() Topics: [releases](), [SDKs]() Tags: [edge](), [release-cadence](), [release-schedule](), [testing](), [two-week-release-cycle](), [uncategorized](), [webdriver](), [webview2]() ### AI overview WebView2 Runtime will align with Microsoft Edge's two-week major-release cadence beginning with version 153. The article explains the updated SDK release approach and recommends preview-channel testing and automated validation for WebView2 apps. ### Source excerpt Microsoft Edge is moving to a two-week release cycle, and the WebView2 is moving to a 2-week release cadence appeared first on Microsoft Edge Blog. ## Episode 67 "Keeping Up With the Java Release Train" \[I/O\] DevFeed: [Episode 67 "Keeping Up With the Java Release Train" \[I/O\]]() Original publisher: [Read original article]() Author: Billy Korando Published: 2026-08-20T00:00:00Z Content type: article Language: en Sources: [Inside Java]() Topics: [Java](), [Development]() Tags: [2026](), [community](), [java](), [jdk](), [release](), [release-cadence]() ### AI overview Episode 67 of the Inside Java Podcast discusses whether organizations can keep up with Java's six-month release cadence. Recorded during JavaOne 2026, Billy Korando interviews SIXT Senior Staff Engineer Danish Nawab about perspectives from outside OpenJDK on the Java ecosystem. ### Source excerpt Since Java moved to a six-month release cadence with JDK 10 in March of 2018, there has been a question if it was practical or possible for organization to keep up with such a release cadence. ## Faster updates, enterprise-friendly schedule: the new Microsoft Edge release cycle DevFeed: [Faster updates, enterprise-friendly schedule: the new Microsoft Edge release cycle]() Original publisher: [Read original article]() Author: Microsoft Edge Team Published: 2026-06-11T16:01:16Z Content type: release Language: en Sources: [Microsoft Edge Blog]() Topics: [Edge](), [Enterprise Preview](), [Microsoft]() Tags: [beta-channel](), [blog](), [browser-management](), [edge](), [edge-for-business](), [enterprise](), [enterprise-deployment](), [enterprise-preview](), [extended-stable](), [microsoft-edge](), [release](), [release-cadence](), [release-schedule](), [stable-channel](), [two-week-release-cycle](), [uncategorized](), [updates]() ### AI overview Microsoft Edge is moving to a two-week Stable release cycle starting with Edge 152 on August 27. Extended Stable will continue receiving updates every eight weeks, with feature updates arriving every fourth release. The article recommends piloting Beta through Enterprise Preview to help organizations validate changes before Stable releases. ### Source excerpt Microsoft Edge is moving to a two-week release cycle, bringing new features and improvements to users and organizations faster than ever. This is great news for teams that thrive on innovation: instead of waiting a full month for the next update, you The post Faster updates, enterprise-friendly schedule: the new Microsoft Edge release cycle appeared first on Microsoft Edge Blog. ## Gateway API v1.5: Moving features to Stable DevFeed: [Gateway API v1.5: Moving features to Stable]() Original publisher: [Read original article]() Published: 2026-04-21T16:30:00Z Content type: release Language: en Sources: [Kubernetes Blog]() Topics: [API](), [Network](), [TLS (Transport Layer Security)](), [Scalability]() Tags: [api](), [community](), [contributors](), [kubernetes](), [network](), [release](), [release-cadence](), [scalability](), [tls]() ### AI overview Gateway API v1.5 promotes six features from Experimental to Standard, including ListenerSet, TLSRoute, HTTPRoute, CORS Filter, client certificate validation, certificate selection for Gateway TLS origination, and ReferenceGrant. The release also introduces a release-train process intended to improve cadence and documentation readiness. ### Source excerpt The Kubernetes SIG Network community presents the release of Gateway API (v1.5)! Released on February 27, 2026, version 1.5 is our biggest release yet, and concentrates on moving existing Experimental features to Standard (Stable). The Gateway API v1.5.1 patch release is already available. The Gateway API v1.5 brings six widely-requested feature promotions to the Standard channel (Gateway API's GA release channel): ListenerSet TLSRoute HTTPRoute CORS Filter Client Certificate Validation Certificate Selection for Gateway TLS Origination ReferenceGrant Special thanks for Gateway API Contributors for their efforts on this release. New release process As of Gateway API v1.5, the project has moved to a release train model, where on a feature freeze date, any features that are ready are shipped in the release. This applies to both Experimental and Standard, and also applies to documentation -- if the documentation isn't ready to ship, the feature isn't ready to ship. We are aiming for this to produce a more reliable release cadence (since we are basing our work off the excellent work done by SIG Release on Kubernetes itself). As part of this change, we've also introduced Release Manager and Release Shadow roles to our release team. Many thanks to Flynn (Buoyant) and Beka Modebadze (Google) for all the great work coordinating and filing the rough edges of our release process. They are both going to continue in this role for the next release as well. New standard featuresListenerSet Leads: Dave Protasowski, David Jumani GEP-1713 Why ListenerSet? Prior to ListenerSet, all listeners had to be specified directly on the Gateway object. While this worked well for simple use cases, it created challenges for more complex or multi-tenant environments: Platform teams and application teams often needed to coordinate changes to the same Gateway Safely delegating ownership of individual listeners was difficult Extending existing Gateways required direct modification of the original res ## PowerShell 7.6 release postmortem and investments DevFeed: [PowerShell 7.6 release postmortem and investments]() Original publisher: [Read original article]() Author: Jason Helmick Published: 2026-04-01T21:01:54Z Content type: article Language: en Sources: [PowerShell Team]() Topics: [PowerShell](), [PowerShell Release](), [releases](), [bug](), [Tooling](), [GitHub](), [Microsoft]() Tags: [bug](), [building](), [compliance](), [github](), [microsoft](), [nuget](), [post](), [powershell](), [powershell-release](), [release](), [release-cadence](), [release-schedule](), [releases](), [systems](), [testing](), [tooling](), [validation](), [windows]() ### AI overview This postmortem explains why PowerShell 7.6 shipped in March 2026 instead of earlier as planned. It examines packaging, compliance, validation, release coordination, holiday freezes, and publishing constraints, and outlines changes intended to improve release predictability and transparency. ### Source excerpt This post shares context on the delayed timing of the PowerShell 7.6 release, our learnings, and the changes the team has already begun making to improve release predictability and transparency. The post PowerShell 7.6 release postmortem and investments appeared first on PowerShell Team. ## How Continuous Delivery Improves Mobile Developer Productivity DevFeed: [How Continuous Delivery Improves Mobile Developer Productivity]() Original publisher: [Read original article]() Author: Ben Published: 2023-07-07T09:58:55Z Content type: article Language: en Sources: [Novoda]() Topics: [Mobile](), [Continuous Delivery (CD)](), [code productivity](), [Release Management](), [Testing]() Tags: [automated](), [ci-cd](), [continuous-delivery](), [developer-productivity](), [engineering](), [mobile](), [mobile-engineering](), [release-cadence]() ### AI overview This article explains how continuous delivery can improve productivity for mobile development teams. It discusses adapting CI/CD practices to mobile constraints, shortening feedback cycles, automating testing, finding bugs faster, and using weekly or fortnightly release cadences to support continual iteration. ### Source excerpt When properly implemented, continuous delivery practices and processes allow your mobile teams to build and deploy products at a much faster rate by improving developer productivity. We explore how. The post How Continuous Delivery Improves Mobile Developer Productivity appeared first on Novoda. ## 2022 Year In Review DevFeed: [2022 Year In Review]() Original publisher: [Read original article]() Published: 2023-01-01T00:00:00Z Content type: article Language: en Sources: [The Vue Point]() Topics: [Vue.js](), [Tooling](), [TypeScript](), [Vite](), [Nuxt.js](), [NativeScript](), [npm](), [Quasar](), [Ionic]() Tags: [developer-experience](), [nativescript](), [npm](), [nuxt](), [quasar](), [recap](), [release-cadence](), [releases](), [tooling](), [typescript](), [vite](), [vue](), [year-in-review]() ### AI overview Vue's 2022 year-in-review covers the transition to Vue 3 as the default, improvements to documentation, tooling, IDE and TypeScript support, ecosystem growth, and support for both Vue 2 and Vue 3. It also outlines plans for smaller and more frequent Vue 3 releases in 2023. ### Source excerpt Happy new year, Vue community! With 2023 upon us, we would like to take this opportunity to recap what happened in 2022, and discuss what to expect in 2023. ## Implementing Server-Driven UI Architecture on the Shop App DevFeed: [Implementing Server-Driven UI Architecture on the Shop App]() Original publisher: [Read original article]() Author: Ashwin Narayanan Published: 2022-11-22T16:00:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Mobile](), [ui](), [Shopify](), [App](), [Development]() Tags: [architecture](), [experiments](), [intern](), [mobile](), [release-cadence](), [server-driven-ui](), [shopify](), [ui]() ### AI overview Shopify's Shop Store team implemented server-driven UI for the Shop App's Store Screen. The architecture lets the server control store sections and customize layouts for different merchants, while addressing component reuse, compatibility with older clients, and faster experimentation. ### Source excerpt Ashwin explains why and how we implemented server-driven UI in the Shop App's Store Screen, and his experience working on the project as a Dev Degree intern. ## Changes to Release Schedule DevFeed: [Changes to Release Schedule]() Original publisher: [Read original article]() Published: 2020-04-03T20:26:28Z Content type: news Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [releases]() Tags: [node-js](), [release](), [release-cadence](), [release-schedule]() ### AI overview Node.js announces adjustments to its release schedule in response to changed work schedules and the global pandemic. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Keycloak Releases and Versioning DevFeed: [Keycloak Releases and Versioning]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2019-04-24T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [releases](), [Continuous Delivery (CD)](), [version](), [deprecated](), [migration](), [API](), [Keycloak](), [Vulnerabilities]() Tags: [continuous-delivery](), [deprecated](), [idm](), [kerberos](), [keycloak](), [ldap](), [migration](), [migration-guide](), [openid-connect](), [preview](), [release](), [release-cadence](), [releases](), [saml](), [security-vulnerabilities](), [sso](), [versioning]() ### AI overview Keycloak describes changes to its release cadence and versioning to support continuous delivery. Feature releases will occur roughly four times a year and increment the major version, while individual features may be marked as preview. The project also plans more frequent micro releases focused on critical bugs and security vulnerabilities. ### Source excerpt We are aiming to achieve a continuous delivery model with Keycloak. By that we mean it should be seamless to upgrade between Keycloak releases and to keep up to date with the latest release. This requires no breaking changes, but rather deprecating old APIs allowing time to migrate to new APIs. Traditional semantic versioning does not fit very well with this model. By following the mantra of continuous delivery we would forever be stuck on a major version and only update the minor version, and you could argue whether or not it would be correct to update the major version when an API that has been deprecated for a long period of time is removed. With this in mind, we have made some slight changes to our release cadence and versioning schema. For now, we will have a new feature release roughly 4 times each year. Each release will bump the major version number. That doesn't mean there are breaking changes, but until we perfect our continuous delivery model there may be some, so always refer to the migration guide prior to upgrading! We have also decided to drop the Final suffix from releases. That is simply because it is not needed as we have not done any beta or release candidates for a long time. In the spirit of continuous delivery, we will have individual features marked as preview rather than whole releases. As a final note, with the reduced release cadence we are planning to do more micro releases. This will be focused on critical bugs and security vulnerabilities. However, we may accept contributions to less critical bugs given the fix is well tested and has low risk of regressions.