1.9.x.x will be the last AdvancedInstaller update and will install as normal.The switch from AdvancedInstaller to Squirrel will involve a number of changes you should be aware of: After each update, SourceTree will regenerate a new release percentage, ensuring a random distribution of updates. SourceTree will check at start up for any new updates, or the check can be manually triggered via the Tools/Options/Update tab. SourceTree generates a release percentage for this local install this defines which part of the release schedule the instance falls into. Overall we felt the user install experience is much improved.įor progressive rollouts, Squirrel comes with built-in staged rollout functionality. The resulting installer is much smaller, quicker to run, has a cleaner footprint, and comes with the added bonus of removing the requirement for Admin rights to install. We’ve found it very easy to integrate Squirrel with our FAKE-based build process and CI. From an app developer’s side, it should be really straightforward to create an installer for my app, and publish updates to it, without having to jump through insane hoops. Windows apps should be as fast and as easy to install and update as apps like Google Chrome. Why Squirrel? We were attracted by its focus on simplicity and felt it aligned well with our goal of improving the installation process for users: Having implemented Squirrel.Windows for SourceTree’s beta program, we’ve decided to move GA releases from AdvancedInstaller to Squirrel as well. no impact on existing alpha/beta distribution.ability to release in stages (group 1 at 5%, group 2 at 15%, etc.).The implementation is slightly different for Windows and macOS platforms, but aim to achieve the same goals: Once a release leaves beta it’s progressively rolled out to groups of users over a period of a few weeks, with time in-between for fixes to be implemented where necessary. The below diagram – using our upcoming 2.4 macOS release as an example – outlines our process and describes the granularity of our new staged rollout in more detail. ![]() The general flow of a build through our release pipeline is common across both Windows and Mac platforms. This staged approach offers the SourceTree team granularity during a release, allowing us to scrutinize each update for bugs and showstoppers before it hits critical mass. Where we used to roll a new update to all users on day one, we’re now progressively rolling out updates to users. By progressively rolling out updates we aim to deliver new features and functionality to users in a more robust fashion. When it comes to rolling out new software updates, the SourceTree team is always looking to deliver a better experience to users with minimal disruption. In the past we an nounced a beta program for SourceTree, detailed how we deliver releases, and now we’re modifying how we roll updates out to users. ![]() Adding staged updates to SourceTree By Brian Ganninger on November 16, 2016
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |