Post by habibkhan1 on Jan 9, 2024 3:52:30 GMT
Google has revealed through a blog post , their plans to transition to a release cycle model for their Chrome web browser, for a brief. Google mentions that the reason for making the change is to reduce the time between creating a new category and starting the beta test , in which the beta version will be created two days after the category is created, instead of the current model which is 8 days. The beta will continue to wait for four weeks. Therefore, the preparation method for the new release will be shortened by one week. Regarding this new model that is planned to be adopted in Chrome, it is worth mentioning that It has been something similar to the recent update of the muse by Canonical in Ubuntu (I do not know at the time if they are supported or taken as basic). And he has the Canonical model 4/2 , this seeks to be able to address the correction of weaknesses in a short time. As mentioned, Canonical's new 4/2 model is based on the fact that two weeks after the start of the next generation of SRU (Sustainable Release Updates), a separate SU update will be published, which only includes fixes for risk. weaknesses and critical issues. For example, in the case of the new Chrome model, take the Chrome branch 119 as an example, it is mentioned that with the previous model the version of this version will be expected on October 3, but with the new model it will arrive on October .
2, while the release of the beta version instead of being released on October 11 (previous model), will be B2B Email List released on October 4 (three days after the release of the stable version and as for the next stable release which will be Chrome 120, instead of coming in November 7, will be launched on October 31. Moreover, he also mentioned that the generation rate of intermediate updates with vulnerabilities has been shortened recently, with which he hopes that the change will be beneficial when testing fixes and finding errors. Although it is also mentioned that one of the negative points of the change is that hackers can take advantage of the appearance of these fixes and develop exploits to use against browser users who have not received the fix (the use of a known security issue and patched is known as n-day exploitation). Chrome releases a new major feature every four weeks. Between those major releases, we deliver updates to fix security bugs and other high-impact bugs. We currently schedule one stable channel update (or "Stability Update") between each major event. Starting with Chrome 116, stability updates will be released every week between major events. And, if it was earlier, within 4 weeks of creating a new version, corrective updates are published two weeks after the next version, starting with Chrome 116, these updates start to be created every week in front weaknesses. In the case of major exceptions or vulnerabilities that have already been used, as before, an update will be released in the schedule.
It is worth mentioning that for those who are interested in knowing the Chrome roadmap, you can contact it from the following link, while to check the Chromium release schedule, you can contact the information in this link. As a personal comment, I can say that trying to deal with security issues and bug fixes in short periods is the best thing for users, but further shortening the stable release cycle can lead to such conflict with users, in addition to the truth. that the new releases, for the most part, can only be corrections and some improvements and will not show new features or additions in functionality as we did before. Finally if you are interested in knowing more about it , you can check the details in the following link. The content of the article adheres to our guidelines of editorial guidelines . To report an error click here . Full path to the article: Linux Addicts » General » Noticias » Chrome makes changes to the release cycle and integrates one similar to Ubuntu's 4/2 News in your email Get the latest Linux news in your email name email I accept legal positions "You're doing it wrong", or why you should find out before you complain (I'm the first) Pablinux 04/01/2024 You are making a mistake You are making a mistake . It's a simple phrase that became famous, with some irony, after Steve Jobs said something similar because of a design flaw in the iPhone 4: by holding it in a strange way, you can make a bridge between the antennas and reduce the signal local power. . He later apologized, saying that if they find humanity and make a mistake, give away bumpers for everyone and return the money to the person who asked.
2, while the release of the beta version instead of being released on October 11 (previous model), will be B2B Email List released on October 4 (three days after the release of the stable version and as for the next stable release which will be Chrome 120, instead of coming in November 7, will be launched on October 31. Moreover, he also mentioned that the generation rate of intermediate updates with vulnerabilities has been shortened recently, with which he hopes that the change will be beneficial when testing fixes and finding errors. Although it is also mentioned that one of the negative points of the change is that hackers can take advantage of the appearance of these fixes and develop exploits to use against browser users who have not received the fix (the use of a known security issue and patched is known as n-day exploitation). Chrome releases a new major feature every four weeks. Between those major releases, we deliver updates to fix security bugs and other high-impact bugs. We currently schedule one stable channel update (or "Stability Update") between each major event. Starting with Chrome 116, stability updates will be released every week between major events. And, if it was earlier, within 4 weeks of creating a new version, corrective updates are published two weeks after the next version, starting with Chrome 116, these updates start to be created every week in front weaknesses. In the case of major exceptions or vulnerabilities that have already been used, as before, an update will be released in the schedule.
It is worth mentioning that for those who are interested in knowing the Chrome roadmap, you can contact it from the following link, while to check the Chromium release schedule, you can contact the information in this link. As a personal comment, I can say that trying to deal with security issues and bug fixes in short periods is the best thing for users, but further shortening the stable release cycle can lead to such conflict with users, in addition to the truth. that the new releases, for the most part, can only be corrections and some improvements and will not show new features or additions in functionality as we did before. Finally if you are interested in knowing more about it , you can check the details in the following link. The content of the article adheres to our guidelines of editorial guidelines . To report an error click here . Full path to the article: Linux Addicts » General » Noticias » Chrome makes changes to the release cycle and integrates one similar to Ubuntu's 4/2 News in your email Get the latest Linux news in your email name email I accept legal positions "You're doing it wrong", or why you should find out before you complain (I'm the first) Pablinux 04/01/2024 You are making a mistake You are making a mistake . It's a simple phrase that became famous, with some irony, after Steve Jobs said something similar because of a design flaw in the iPhone 4: by holding it in a strange way, you can make a bridge between the antennas and reduce the signal local power. . He later apologized, saying that if they find humanity and make a mistake, give away bumpers for everyone and return the money to the person who asked.