Chrome release cycle
Download as ppt, pdf1 like4,336 views
The document describes Chrome's release cycle philosophy and process. It aimed to [1] shorten release cycles and branch lifespan, [2] make releases more predictable and scoped, and [3] reduce team strain. Originally releases took 1-3 months and were unpredictable. The new process uses overlapping 11-week schedules for 3 channels, with branch points every 6 weeks to control scope. Features must be engineered to disable easily. Only stability/security fixes can block releases. The process improved predictability while allowing ongoing feature development.
1 of 21
Downloaded 45 times
Ad
Recommended
Introduzione a Docker
Introduzione a DockerRoberto Messora Il documento offre un'introduzione a Docker, una tecnologia open-source per il deployment di applicazioni in container, evidenziando la sua capacità di isolare software dagli ambienti di esecuzione e ottimizzare l'uso delle risorse hardware. Include anche una panoramica sulla storia di Docker e spiega come funziona sia su Linux che su Windows, con dettagli sui diversi tipi di container e sul suo ecosistema. Infine, discute l'uso di Docker in produzione e le sue integrazioni con altri strumenti di orchestrazione come Kubernetes e Docker Swarm.
Docker Security workshop slides
Docker Security workshop slidesDocker, Inc. The workshop focuses on Docker security, covering features, tools, best practices, and practical exercises on securing Docker environments. It includes understanding container architecture, namespaces, control groups, and implementing TLS for secure communications. Additionally, it discusses security practices like minimal base images, image provenance, Docker content trust, capabilities management, and seccomp configurations.
Docker and the Linux Kernel
Docker and the Linux KernelDocker, Inc. The document summarizes a talk given at the Linux Plumbers Conference 2014 about Docker and the Linux kernel. It discusses what Docker is, how it uses kernel features like namespaces and cgroups, its different storage drivers and their issues, kernel requirements, and how Docker and kernel developers can collaborate to test and improve the kernel and Docker software.
Tutoriel GIT
Tutoriel GITFrancois ANDRE Ce document présente les principes fondamentaux de l'utilisation de Git pour la gestion de version dans le développement collaboratif. Il décrit comment Git permet de travailler sur plusieurs versions d'un projet, manage l'historique des modifications, et facilite la collaboration entre développeurs. Les aspects pratiques et les commandes essentielles sont également abordés, notamment la création de dépôts, l'indexation des modifications et la gestion des branches.
Docker 101: An Introduction
Docker 101: An IntroductionPOSSCON This document provides an introduction to Docker presented by Tibor Vass, a core maintainer on Docker Engine. It outlines challenges with traditional application deployment and argues that Docker addresses these by providing lightweight containers that package code and dependencies. The key Docker concepts of images, containers, builds and Compose are introduced. Images are read-only templates for containers which sandbox applications. Builds describe how to assemble images with Dockerfiles. Compose allows defining multi-container applications. The document concludes by describing how Docker improves the deployment workflow by allowing testing and deployment of the same images across environments.
Docker on Docker
Docker on DockerDocker, Inc. This document discusses Docker Inc's transition to running their infrastructure on Docker EE (Docker Enterprise Edition). Some key points:
- Previously Docker Inc ran their infrastructure (Docker Hub, Docker Store, etc) on a collection of Docker hosts managed imperatively without orchestration.
- They transitioned to running everything on Docker EE for the benefits of declarative orchestration using Docker Swarm, access controls, and resource management.
- The transition was done by changing the orchestration layer only, without changing applications, containers, logs, metrics, etc. This allowed them to gradually transition services to Docker EE.
- Running as a customer of their own product has provided Docker Inc valuable insights into best practices, feature requests
Deep Dive into the AOSP
Deep Dive into the AOSPDr. Ketan Parmar This document provides an overview of the steps to build and install the Android Open Source Project (AOSP) from source. It discusses initializing a build environment, downloading the AOSP source tree and device drivers, building and installing the AOSP build on a Nexus 5 device. The build process involves initializing a repo client, syncing the source code, choosing a target, and running make. The installed AOSP build can then be used to power an unlocked Nexus 5 device.
Platform as reflection of values: Joyent, node.js, and beyond
Platform as reflection of values: Joyent, node.js, and beyondbcantrill This document discusses how software platform decisions reflect the values of their communities. It outlines many values that platforms may aspire to, such as debuggability, robustness, and stability. However, it notes that platforms must balance these values, and different communities will prioritize certain "core values" over others. The document traces how Joyent's values diverged from those of the node.js community, particularly around priorities like compatibility versus robustness. It argues that values should be clearly defined and notes the challenges that arise when a platform's and organization's values do not align.
Docker Swarm 0.2.0
Docker Swarm 0.2.0Docker, Inc. The document introduces Docker Swarm, a clustering system that allows multiple Docker engines to be managed as a single entity, highlighting its functionality, resource management capabilities, and the ease of getting started. It outlines features such as advanced scheduling, node management, and custom constraints, along with its upcoming integration with various backends and high availability options. The document also includes key commands for creating and managing clusters, as well as an invitation for community contributions.
A deep dive into Android OpenSource Project(AOSP)
A deep dive into Android OpenSource Project(AOSP)Siji Sunny The document details the history and architecture of the Android Open Source Project, originally founded as Android, Inc. in 2003 and acquired by Google in 2005. It covers key components such as the Linux kernel, hardware abstraction layer, and noteworthy features of the Dalvik VM. Additionally, it explains the structure and communication mechanisms within the Android platform, including the role of libraries and core services.
Docker Online Meetup #22: Docker Networking
Docker Online Meetup #22: Docker NetworkingDocker, Inc. The document discusses the importance of networking in distributed applications and the goals of Docker networking, including making networks a first-class object and providing a pluggable networking stack. It introduces 'libnetwork', an open-sourced library for managing container network stacks, detailing features such as service discovery and various network driver implementations. The document also outlines future plans for enhancements, calling the community to try the Docker experimental channel and contribute to libnetwork.
presentation on Docker
presentation on DockerVirendra Ruhela Docker is an open platform for developing, shipping, and running distributed applications. It allows applications to be shipped and run in lightweight containers that can run on any Linux server. Docker uses operating-system-level virtualization and cgroups isolation to deliver lightweight containers quickly. Key features of Docker include portability, lightweight containers that share resources and isolate processes, and automated workflows.
Apresentação UX e UI - Webdesign - Aula 07
Apresentação UX e UI - Webdesign - Aula 07Renato Melo O documento discute experiência do usuário (UX) e interface do usuário (UI) na web. Apresenta como os usuários interagem com a internet de forma diferente dependendo da idade e como UX e UI melhoram a satisfação do cliente através de estratégias como simplificar formulários e destacar a conversão.
VMware Tanzu Kubernetes Connect
VMware Tanzu Kubernetes ConnectVMware Tanzu This document provides an agenda and materials for a workshop on VMware Tanzu for Kubernetes Operations. The agenda includes an introduction to challenges faced by platform teams maintaining Kubernetes platforms, an overview of Tanzu for Kubernetes Operations and how it can help address those challenges, and a hands-on lab session. Tanzu for Kubernetes Operations is a collection of products that provide capabilities for common customer needs around managing containerized platforms at scale, including simplified management of Kubernetes clusters across clouds, centralized visibility and security policies, and developer self-service access.
An Insight into the Linux Booting Process
An Insight into the Linux Booting ProcessHardeep Bhurji The document details the Linux booting process, starting from the BIOS and the execution of the bootloader, to loading the Linux kernel and the initial RAM disk (initrd). It describes the roles of both LILO and GRUB boot loaders during the boot sequence, emphasizing GRUB's flexibility over LILO. Finally, it explains the initialization of system processes, including the execution of the init program and the management of runlevels within the Linux system.
[C++ Korea 2nd Seminar] Ranges for The Cpp Standard Library
[C++ Korea 2nd Seminar] Ranges for The Cpp Standard LibraryDongMin Choi Microsoft Melting Pot
C++ Korea 2nd Seminar
Ranges for The Cpp Standard Library
https://channel9.msdn.com/Events/Channel9-Korea/cplusplus/Ranges-for-The-C-Standard-Library
Guaranteeing Memory Safety in Rust
Guaranteeing Memory Safety in Rustnikomatsakis Rust provides both control and safety through its ownership and borrowing model. It enforces safe patterns using the type system to prevent issues like data races, use-after-free errors, and iterator invalidation. This is achieved with no runtime overhead. Rust also supports building efficient abstractions through features like zero-cost abstractions and its approach to concurrency that guarantees freedom from data races. While Rust borrows ideas from other languages, its type system and ownership rules allow building applications that have control without compromising on safety.
Android SDK Tutorial | Edureka
Android SDK Tutorial | EdurekaEdureka! The Android SDK (Software Development Kit) provides tools for developing Android applications, including an emulator and debugging tools. It covers installation procedures, features, and programming languages used. The document also mentions updates to components like the APK command-line version and ProGuard rules.
Momenti Seminar - 5 Years of RosettaStone
Momenti Seminar - 5 Years of RosettaStoneChris Ohk Momenti Seminar에서 진행했던 "하스스톤 시뮬레이터 RosettaStone 개발 5년 간의 기록"의 발표 자료를 공유드립니다. 5년 동안 오픈 소스 프로젝트를 진행하면서 경험했던 일들을 정리하며 어떤 교훈을 얻었는지 생각해보는 시간이었습니다. 많은 분들에게 도움이 되었으면 합니다.
U Boot or Universal Bootloader
U Boot or Universal BootloaderSatpal Parmar The document provides an overview of Das U-Boot, a universal boot loader used to load operating systems and applications into memory on embedded systems. It discusses U-Boot's features such as its command line interface, ability to load images from different sources, and support for various architectures and boards. It also covers compiling and configuring U-Boot, as well as its basic command set and image support capabilities.
Project meeting: Android Graphics Architecture Overview
Project meeting: Android Graphics Architecture OverviewYu-Hsin Hung The Android graphics architecture uses SurfaceFlinger to composite surfaces from apps into the final display. Apps draw to surfaces using a canvas, which can target OpenGL or a software renderer. Views define a display list of drawing commands. SurfaceFlinger receives surfaces from apps and window status from WindowManager to composite surfaces in z-order before each VSYNC signal.
Version control system
Version control systemAryman Gautam The document provides an overview of version control systems (VCS), detailing their types, history, and the distinction between centralized (CVCS) and distributed (DVCS) systems, with a focus on Git. It explains Git's role as an open-source VCS, its functionalities, and the typical workflow involved in its usage, including Git commands and operations. Additionally, it contrasts Git with GitHub, emphasizing that Git is a tool for tracking versions while GitHub is a cloud hosting service for Git repositories.
Kubernetes in Docker
Kubernetes in DockerDocker, Inc. 1. Docker EE will include an unmodified Kubernetes distribution to provide orchestration capabilities alongside Docker Swarm.
2. When running mixed workloads across orchestrators, resource contention is a risk and it is recommended to separate workloads by orchestrator on each node for now.
3. Docker EE aims to address the shortcomings of running mixed workloads to better support this in the future.
Docker advance topic
Docker advance topicKalkey This document provides an overview of advanced Docker topics including Docker installation, Docker networking using bridges and volumes, and creating Dockerfiles. It discusses installing Docker on CentOS, the different types of Docker networks including bridge, host, overlay and macvlan. It also covers creating and managing Docker volumes, starting containers with volumes, and creating Dockerfiles with components like FROM, RUN, COPY and ENTRYPOINT.
Android Synopsis
Android SynopsisNiraj Rahi This document proposes a college application mobile app that would allow students, faculty, and alumni to easily access college data like login, attendance, schedules, and notifications from their smart devices. It would use an Android open source platform and allow authorized users to insert, update, delete and fetch data from the college website. The app is designed to be cost effective, time saving and reduce power consumption compared to traditional systems. It would provide a simple login and allow users to get, update, insert and delete data as needed.
Affordances (propiciação) em interfaces digitais
Affordances (propiciação) em interfaces digitaisRodrigo Freese Gonzatto O documento discute o conceito de affordance, que é a relação entre uma pessoa e um objeto ou sistema que revela possíveis ações. As affordances percebidas são as qualidades de um objeto ou sistema que permitem determinado desempenho ou ação. Exemplos incluem como as pessoas interagem com encaixes, acoplamentos e interfaces digitais.
Docker introduction
Docker introductionPhuc Nguyen The document introduces Docker, a container platform. It discusses how Docker addresses issues with deploying different PHP projects that have varying version requirements by allowing each project to run isolated in its own container with specified dependencies. It then covers key Docker concepts like images, containers, linking, exposing ports, volumes, and Dockerfiles. The document highlights advantages of Docker like enabling applications to run anywhere without compatibility issues and making deployment more efficient.
DevOps - Cultura e Filosofia
DevOps - Cultura e FilosofiaJônatan Gouveia Jônatan Gouveia, um especialista em DevOps com experiência em automação de sistemas, discute a cultura e filosofia do DevOps, destacando a importância da comunicação, automatização e adoção de microsserviços. O documento abrange práticas como integração contínua, entrega contínua e infraestrutura como código, além de enfatizar a importância da colaboração e monitoramento. Gouveia também fornece diretrizes de estudo para aspirantes a profissionais de DevOps e uma visão sobre o mercado de trabalho na área.
Chrome发布周期
Chrome发布周期36Kr.com The document describes Chrome's release cycle, which aims for predictable, regular releases by adopting an overlapping development model. Key aspects include releasing every 6 weeks on 3 channels, addressing all work on a central trunk before branching for stabilization, and controlling scope by disabling unfinished features at branch points. This approach improved flow by making releases less draining and more predictable compared to long-lived branches and unpredictable cycles under the previous model.
White Paper: Release This! - Tools for a Smooth Release Cycle
White Paper: Release This! - Tools for a Smooth Release CyclePerforce This document discusses an alternative branching strategy used by Guerrilla Games where developers work on the main branch and changes are selectively integrated to release branches. Key points:
- Developers work on main branch while a release branch is used for testing and bug fixes. Changes are integrated from main to release under control of release managers.
- Tools were created to track changes, show dependencies, and facilitate integrations to improve process scalability and visibility for all developers.
- The strategy provides more control over release cycles by decoupling development from releases and allowing targeted testing of features on release branches. Maintaining transparency of changes is important for its success.
More Related Content
What's hot (20)
Docker Swarm 0.2.0
Docker Swarm 0.2.0Docker, Inc. The document introduces Docker Swarm, a clustering system that allows multiple Docker engines to be managed as a single entity, highlighting its functionality, resource management capabilities, and the ease of getting started. It outlines features such as advanced scheduling, node management, and custom constraints, along with its upcoming integration with various backends and high availability options. The document also includes key commands for creating and managing clusters, as well as an invitation for community contributions.
A deep dive into Android OpenSource Project(AOSP)
A deep dive into Android OpenSource Project(AOSP)Siji Sunny The document details the history and architecture of the Android Open Source Project, originally founded as Android, Inc. in 2003 and acquired by Google in 2005. It covers key components such as the Linux kernel, hardware abstraction layer, and noteworthy features of the Dalvik VM. Additionally, it explains the structure and communication mechanisms within the Android platform, including the role of libraries and core services.
Docker Online Meetup #22: Docker Networking
Docker Online Meetup #22: Docker NetworkingDocker, Inc. The document discusses the importance of networking in distributed applications and the goals of Docker networking, including making networks a first-class object and providing a pluggable networking stack. It introduces 'libnetwork', an open-sourced library for managing container network stacks, detailing features such as service discovery and various network driver implementations. The document also outlines future plans for enhancements, calling the community to try the Docker experimental channel and contribute to libnetwork.
presentation on Docker
presentation on DockerVirendra Ruhela Docker is an open platform for developing, shipping, and running distributed applications. It allows applications to be shipped and run in lightweight containers that can run on any Linux server. Docker uses operating-system-level virtualization and cgroups isolation to deliver lightweight containers quickly. Key features of Docker include portability, lightweight containers that share resources and isolate processes, and automated workflows.
Apresentação UX e UI - Webdesign - Aula 07
Apresentação UX e UI - Webdesign - Aula 07Renato Melo O documento discute experiência do usuário (UX) e interface do usuário (UI) na web. Apresenta como os usuários interagem com a internet de forma diferente dependendo da idade e como UX e UI melhoram a satisfação do cliente através de estratégias como simplificar formulários e destacar a conversão.
VMware Tanzu Kubernetes Connect
VMware Tanzu Kubernetes ConnectVMware Tanzu This document provides an agenda and materials for a workshop on VMware Tanzu for Kubernetes Operations. The agenda includes an introduction to challenges faced by platform teams maintaining Kubernetes platforms, an overview of Tanzu for Kubernetes Operations and how it can help address those challenges, and a hands-on lab session. Tanzu for Kubernetes Operations is a collection of products that provide capabilities for common customer needs around managing containerized platforms at scale, including simplified management of Kubernetes clusters across clouds, centralized visibility and security policies, and developer self-service access.
An Insight into the Linux Booting Process
An Insight into the Linux Booting ProcessHardeep Bhurji The document details the Linux booting process, starting from the BIOS and the execution of the bootloader, to loading the Linux kernel and the initial RAM disk (initrd). It describes the roles of both LILO and GRUB boot loaders during the boot sequence, emphasizing GRUB's flexibility over LILO. Finally, it explains the initialization of system processes, including the execution of the init program and the management of runlevels within the Linux system.
[C++ Korea 2nd Seminar] Ranges for The Cpp Standard Library
[C++ Korea 2nd Seminar] Ranges for The Cpp Standard LibraryDongMin Choi Microsoft Melting Pot
C++ Korea 2nd Seminar
Ranges for The Cpp Standard Library
https://channel9.msdn.com/Events/Channel9-Korea/cplusplus/Ranges-for-The-C-Standard-Library
Guaranteeing Memory Safety in Rust
Guaranteeing Memory Safety in Rustnikomatsakis Rust provides both control and safety through its ownership and borrowing model. It enforces safe patterns using the type system to prevent issues like data races, use-after-free errors, and iterator invalidation. This is achieved with no runtime overhead. Rust also supports building efficient abstractions through features like zero-cost abstractions and its approach to concurrency that guarantees freedom from data races. While Rust borrows ideas from other languages, its type system and ownership rules allow building applications that have control without compromising on safety.
Android SDK Tutorial | Edureka
Android SDK Tutorial | EdurekaEdureka! The Android SDK (Software Development Kit) provides tools for developing Android applications, including an emulator and debugging tools. It covers installation procedures, features, and programming languages used. The document also mentions updates to components like the APK command-line version and ProGuard rules.
Momenti Seminar - 5 Years of RosettaStone
Momenti Seminar - 5 Years of RosettaStoneChris Ohk Momenti Seminar에서 진행했던 "하스스톤 시뮬레이터 RosettaStone 개발 5년 간의 기록"의 발표 자료를 공유드립니다. 5년 동안 오픈 소스 프로젝트를 진행하면서 경험했던 일들을 정리하며 어떤 교훈을 얻었는지 생각해보는 시간이었습니다. 많은 분들에게 도움이 되었으면 합니다.
U Boot or Universal Bootloader
U Boot or Universal BootloaderSatpal Parmar The document provides an overview of Das U-Boot, a universal boot loader used to load operating systems and applications into memory on embedded systems. It discusses U-Boot's features such as its command line interface, ability to load images from different sources, and support for various architectures and boards. It also covers compiling and configuring U-Boot, as well as its basic command set and image support capabilities.
Project meeting: Android Graphics Architecture Overview
Project meeting: Android Graphics Architecture OverviewYu-Hsin Hung The Android graphics architecture uses SurfaceFlinger to composite surfaces from apps into the final display. Apps draw to surfaces using a canvas, which can target OpenGL or a software renderer. Views define a display list of drawing commands. SurfaceFlinger receives surfaces from apps and window status from WindowManager to composite surfaces in z-order before each VSYNC signal.
Version control system
Version control systemAryman Gautam The document provides an overview of version control systems (VCS), detailing their types, history, and the distinction between centralized (CVCS) and distributed (DVCS) systems, with a focus on Git. It explains Git's role as an open-source VCS, its functionalities, and the typical workflow involved in its usage, including Git commands and operations. Additionally, it contrasts Git with GitHub, emphasizing that Git is a tool for tracking versions while GitHub is a cloud hosting service for Git repositories.
Kubernetes in Docker
Kubernetes in DockerDocker, Inc. 1. Docker EE will include an unmodified Kubernetes distribution to provide orchestration capabilities alongside Docker Swarm.
2. When running mixed workloads across orchestrators, resource contention is a risk and it is recommended to separate workloads by orchestrator on each node for now.
3. Docker EE aims to address the shortcomings of running mixed workloads to better support this in the future.
Docker advance topic
Docker advance topicKalkey This document provides an overview of advanced Docker topics including Docker installation, Docker networking using bridges and volumes, and creating Dockerfiles. It discusses installing Docker on CentOS, the different types of Docker networks including bridge, host, overlay and macvlan. It also covers creating and managing Docker volumes, starting containers with volumes, and creating Dockerfiles with components like FROM, RUN, COPY and ENTRYPOINT.
Android Synopsis
Android SynopsisNiraj Rahi This document proposes a college application mobile app that would allow students, faculty, and alumni to easily access college data like login, attendance, schedules, and notifications from their smart devices. It would use an Android open source platform and allow authorized users to insert, update, delete and fetch data from the college website. The app is designed to be cost effective, time saving and reduce power consumption compared to traditional systems. It would provide a simple login and allow users to get, update, insert and delete data as needed.
Affordances (propiciação) em interfaces digitais
Affordances (propiciação) em interfaces digitaisRodrigo Freese Gonzatto O documento discute o conceito de affordance, que é a relação entre uma pessoa e um objeto ou sistema que revela possíveis ações. As affordances percebidas são as qualidades de um objeto ou sistema que permitem determinado desempenho ou ação. Exemplos incluem como as pessoas interagem com encaixes, acoplamentos e interfaces digitais.
Docker introduction
Docker introductionPhuc Nguyen The document introduces Docker, a container platform. It discusses how Docker addresses issues with deploying different PHP projects that have varying version requirements by allowing each project to run isolated in its own container with specified dependencies. It then covers key Docker concepts like images, containers, linking, exposing ports, volumes, and Dockerfiles. The document highlights advantages of Docker like enabling applications to run anywhere without compatibility issues and making deployment more efficient.
DevOps - Cultura e Filosofia
DevOps - Cultura e FilosofiaJônatan Gouveia Jônatan Gouveia, um especialista em DevOps com experiência em automação de sistemas, discute a cultura e filosofia do DevOps, destacando a importância da comunicação, automatização e adoção de microsserviços. O documento abrange práticas como integração contínua, entrega contínua e infraestrutura como código, além de enfatizar a importância da colaboração e monitoramento. Gouveia também fornece diretrizes de estudo para aspirantes a profissionais de DevOps e uma visão sobre o mercado de trabalho na área.
Similar to Chrome release cycle (20)
Chrome发布周期
Chrome发布周期36Kr.com The document describes Chrome's release cycle, which aims for predictable, regular releases by adopting an overlapping development model. Key aspects include releasing every 6 weeks on 3 channels, addressing all work on a central trunk before branching for stabilization, and controlling scope by disabling unfinished features at branch points. This approach improved flow by making releases less draining and more predictable compared to long-lived branches and unpredictable cycles under the previous model.
White Paper: Release This! - Tools for a Smooth Release Cycle
White Paper: Release This! - Tools for a Smooth Release CyclePerforce This document discusses an alternative branching strategy used by Guerrilla Games where developers work on the main branch and changes are selectively integrated to release branches. Key points:
- Developers work on main branch while a release branch is used for testing and bug fixes. Changes are integrated from main to release under control of release managers.
- Tools were created to track changes, show dependencies, and facilitate integrations to improve process scalability and visibility for all developers.
- The strategy provides more control over release cycles by decoupling development from releases and allowing targeted testing of features on release branches. Maintaining transparency of changes is important for its success.
The Evolution of Continuous Delivery at Scale @ Linkedin
The Evolution of Continuous Delivery at Scale @ LinkedinC4Media The document outlines the evolution of LinkedIn's software development and continuous delivery practices from 2007 to 2014, highlighting growth from 30 to 1800 developers and the transition from monolithic to independent deployments. Key improvements included automated testing, enhanced developer ownership, and the implementation of a trunk-based development process, which enabled faster and more reliable releases. It emphasizes the significance of culture, tooling, and processes in achieving successful software delivery at scale.
2012 - A Release Odyssey
2012 - A Release OdysseyErnest Mueller Ernest Mueller from Bazaarvoice discusses their journey from a ten-week release cycle to biweekly and then weekly releases for their substantial legacy application, which consists of 4.9 million lines of code. Key improvements included hiring QA automation personnel, introducing testing sprints, and implementing feature flagging, leading to a significant reduction in reported client issues. The ongoing enhancements aim for continuous deployment and improved build systems as the organization adapts to agile methodologies.
Pusheando en master, que es gerundio
Pusheando en master, que es gerundioIsidro José López Martínez This document provides an overview of trunk-based development. It begins with defining continuous integration, delivery, deployment, and release. It then discusses branching strategies like GitFlow and the problems with pull requests. Trunk-based development is presented as pushing code directly to the main branch, along with practices like pairing, feature flags, and continuous delivery pipelines. The document stresses trunk-based development is about more than just the branch - it requires risk management, delivering value, and technical excellence. It provides advice on when not to use it and how to start implementing it.
Branching and Merging Practices
Branching and Merging Practices Rajesh Kumar This document discusses different branching and merging practices for managing code in source control. It describes branch by release patterns where different branches are maintained for each release. It also covers branch by quality where branches are used to isolate different code quality stages. Branch by feature is presented as another option where branches are used to isolate development of independent features. The document provides examples and considerations for selecting the appropriate branching strategy based on factors like project needs and timelines.
ETCA_8
ETCA_8PMI2011 The document describes a framework developed by Venkatraman L. to manage multiple simultaneous releases across multiple teams using Agile Scrum and Kanban. The framework was needed as a startup scaled and required a more structured approach to managing over 30 parallel releases involving different teams. The framework focuses on release dependency mapping, inter-team coordination, release planning, and sprint planning while maintaining team velocity. It uses a mix of "push" by adding items to team backlogs, and "pull" via Kanban during execution. Key elements include portfolio item prioritization, release vs deployment definitions, and roles of various teams in the process.
Party of One
Party of OneKirill Grouchnikov The document provides advice for developing, maintaining, and promoting open source hobby projects on SourceForge. It discusses establishing release schedules with regular major releases every year, prioritizing bug fixes and code health over new features, using task schedules to coordinate development, and the importance of documentation, testing, and blogging to promote releases.
A real-life overview of Agile and Scrum
A real-life overview of Agile and Scrummtoppa The document presents an extensive overview of Scrum, emphasizing its core principles, roles, and practices in agile software development. It discusses the misalignment of authority and responsibility in organizations, the importance of feedback in development, and the adoption of Scrum to improve project outcomes. Additionally, it highlights common challenges and anti-patterns in Scrum implementation, offering best practices and recommendations for successful adoption.
Agile Product Owner
Agile Product OwnerAaron Sanders The document outlines the role and responsibilities of an Agile Product Owner, emphasizing the significance of making profitable software development decisions, managing the product backlog, and prioritizing user stories based on expected ROI. It addresses challenges faced by Product Owners and illustrates various planning waves for product, release, feature, and story levels while highlighting the importance of incremental funding methodology and understanding market needs. Additionally, it discusses strategies for prioritizing features and maximizing return on investment through effective release planning.
Rilasciamo rilasciamo
Rilasciamo rilasciamoFrancesco Mapelli The document outlines the transition of a development team from releasing three times a year to biweekly iterations, detailing the challenges, fears, and successes encountered during this shift. Key points include the team's adaptation to a more flexible release process, improved responsiveness to user feedback, and growing agility within the company. The emphasis is on the importance of collaboration, planning, and continuous improvement in delivering scalable and production-ready features.
Release This! - Tools for a Smooth Release Cycle
Release This! - Tools for a Smooth Release CyclePerforce The document discusses the challenges of managing a release cycle in software development, particularly highlighting the issues with large codebases and the old release process. It presents an improved methodology that involves working on the main branch and integrating selected fixes into a stabilization release, enhancing control and visibility. The document concludes with a discussion on the limitations of this process and suggests further improvements for effective release management.
What the music of the 1980s taught me about shipping software
What the music of the 1980s taught me about shipping softwareMichael Ewins The document details the processes and considerations involved in shipping software products and managing software releases. It emphasizes the importance of effective communication, performance monitoring, and maintaining a streamlined development workflow with version control, testing, and deployment strategies. Additionally, it provides insights into addressing challenges such as data migration, customer support, and release management to enhance team efficiency and product delivery.
Scaling Up Lookout
Scaling Up LookoutLookout The speaker discusses how Lookout has scaled its engineering organization and technical infrastructure over time. In 2011, Lookout had problems with unreliable deployments and a monolithic codebase. It introduced new tools like JIRA, Jenkins, and Git/Gerrit to improve its workflow. It also automated deployments and now has a much higher success rate. As Lookout has grown, it has moved to a more distributed architecture with over 100 microservices running on different technologies. Scaling organizational knowledge and coordinating many independent services will be ongoing challenges.
Release Engineering
Release EngineeringGDG Odessa Oleg Chorny discusses Google's approach to release engineering, which aims to reduce manual toil through automation. Some key aspects include establishing frequent release cycles to catch bugs early, empowering individual teams through self-service tools and best practices, integrating automated testing, packaging, deployment and configuration management into the release process, and defining clear policies for approving and controlling releases. The overall goal is to make software releases as simple as pressing a button by establishing the right automated systems and collaboration between developers and release engineers.
Continuous delivery the french way Agile Cambridge 2014
Continuous delivery the french way Agile Cambridge 2014Dimitri Baeli The document discusses the evolution of continuous delivery practices at LesFurets, highlighting their transition from a traditional release model to a more agile approach with faster builds and daily releases. It emphasizes the importance of continuous integration, automated testing, and operational monitoring while incorporating methodologies like Kanban and Git flow. The document also includes references to various tools and principles that support efficient software delivery, showcasing the team's commitment to maintaining high code quality and quick turnaround times.
A real-life overview of Agile workflow practices
A real-life overview of Agile workflow practicesmtoppa The document provides an overview of agile workflow practices, emphasizing the importance of flexible, iterative approaches over the traditional waterfall model in software development. It shares the author's experiences in implementing scrum methodologies, highlights the challenges faced during transitions, and discusses the necessity of roles such as product owner and scrum master. The text also explores how agile practices can enhance collaboration, improve project management, and adapt to changing client needs.
Doing agile with an ISO-20000 Telco (AgilePT 2015)
Doing agile with an ISO-20000 Telco (AgilePT 2015)Manuel Padilha The document discusses the challenges and strategies of implementing agile practices in a software development project for a telecommunications company involving two distinct organizational cultures. It emphasizes the importance of maintaining flexibility in scope while adhering to a structured project management framework, despite cultural clashes and differing priorities between the small development team and the large company's management. The project evolves through distinct phases, highlighting effective team communication, sprint management, and the eventual need for professional project management to mitigate risks before deployment.
Introduction to Scrum
Introduction to ScrumBixlabs We usually work with clients using time and materials, fixed price per release, or fixed price for the entire project. For the first two approaches, we use scrum artifacts like the product backlog and sprints. The product backlog contains prioritized user stories, bugs, and improvements. We refine stories in refinement meetings and plan each sprint in sprint planning meetings. Daily standup meetings keep the team synchronized. At the end of each sprint, we demo completed work and retrospect on our process in retrospective meetings.
Timeboxed releases - Peter Antman
Timeboxed releases - Peter Antmanmanssandstrom The document discusses principles for agile software development and releasing software in a continuous manner. It outlines five steps to achieve this: 1) Learn how to plan in small iterations, 2) Organize delivery to keep focus and avoid issues, 3) Automate everything for traceability, 4) Test everything continuously, and 5) Always integrate code to ensure releases are always releasable. The goal is to release software early and often through a process of timeboxed iterations, continuous integration, and automated testing.
Ad
Recently uploaded (20)
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...Fwdays Let's talk about our history. How we started the project with a small vector database of less than 2 million records. Later, we received a request for +100 million records, then another +100... And so gradually we reached almost 1 billion. Standard tools were quickly running out of steam - we were running into performance, index size, and very limited resources. After a long series of trials and errors, we built our own low-cost cluster, which today stably processes thousands of queries to more than 1B vectors.
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...Edge AI and Vision Alliance For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2025/06/mpu-a-transformative-solution-for-next-gen-ai-at-the-edge-a-presentation-from-fotonation/
Petronel Bigioi, CEO of FotoNation, presents the “MPU+: A Transformative Solution for Next-Gen AI at the Edge” tutorial at the May 2025 Embedded Vision Summit.
In this talk, Bigioi introduces MPU+, a novel programmable, customizable low-power platform for real-time, localized intelligence at the edge. The platform includes an AI-augmented image signal processor that enables leading image and video quality.
In addition, it integrates ultra-low-power object and motion detection capabilities to enable always-on computer vision. A programmable neural processor provides flexibility to efficiently implement new neural networks. And additional specialized engines facilitate image stabilization and audio enhancements.
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019 A presentation at Internetware 2025.
Agentic AI for Developers and Data Scientists Build an AI Agent in 10 Lines o...
Agentic AI for Developers and Data Scientists Build an AI Agent in 10 Lines o...All Things Open Presented at All Things Open RTP Meetup
Presented by William Hill - Developer Advocate, NVIDIA
Title: Agentic AI for Developers and Data Scientists
Build an AI Agent in 10 Lines of Code and the Concepts Behind the Code
Abstract: In this talk we will demonstrate building a working data science AI agent in 10 lines of basic Python code in a Colab notebook. Our AI Agent will perform LLM prompt-driven visual analysis using open-source libraries. In this session we will show how to develop an AI Agent using GPUs through NVIDIA’s developer program and Google Colab notebooks. After coding our AI Agent, we will break down the 10 lines of code. We will show the key components and open source library integrations that enable the agent's functionality, focusing on practical implementation details and then the theoretical concepts. The presentation concludes with a survey of current LLM technologies and the latest trends in developing AI applications for enthusiasts and enterprises
cnc-processing-centers-centateq-p-110-en.pdf
cnc-processing-centers-centateq-p-110-en.pdfAmirStern2 מרכז עיבודים תעשייתי בעל 3/4/5 צירים, עד 22 החלפות כלים עם כל אפשרויות העיבוד הדרושות. בעל שטח עבודה גדול ומחשב נוח וקל להפעלה בשפה העברית/רוסית/אנגלית/ספרדית/ערבית ועוד..
מסוגל לבצע פעולות עיבוד שונות המתאימות לענפים שונים: קידוח אנכי, אופקי, ניסור, וכרסום אנכי.
Smarter Aviation Data Management: Lessons from Swedavia Airports and Sweco
Smarter Aviation Data Management: Lessons from Swedavia Airports and SwecoSafe Software Managing airport and airspace data is no small task, especially when you’re expected to deliver it in AIXM format without spending a fortune on specialized tools. But what if there was a smarter, more affordable way?
Join us for a behind-the-scenes look at how Sweco partnered with Swedavia, the Swedish airport operator, to solve this challenge using FME and Esri.
Learn how they built automated workflows to manage periodic updates, merge airspace data, and support data extracts – all while meeting strict government reporting requirements to the Civil Aviation Administration of Sweden.
Even better? Swedavia built custom services and applications that use the FME Flow REST API to trigger jobs and retrieve results – streamlining tasks like securing the quality of new surveyor data, creating permdelta and baseline representations in the AIS schema, and generating AIXM extracts from their AIS data.
To conclude, FME expert Dean Hintz will walk through a GeoBorders reading workflow and highlight recent enhancements to FME’s AIXM (Aeronautical Information Exchange Model) processing and interpretation capabilities.
Discover how airports like Swedavia are harnessing the power of FME to simplify aviation data management, and how you can too.
The Growing Value and Application of FME & GenAI
The Growing Value and Application of FME & GenAISafe Software With the cost of using Generative AI services dropping exponentially and the array of available models continually expanding, integrating AI into FME workflows has become inexpensive, accessible and effective. This presentation explores how GenAI within FME can cost-effectively transform data workflows by automating data extraction, validation, classification and augmentation tasks. We’ll discuss how FME’s no-code flexibility enables users to combine Generative AI and Computer Vision tools that create efficient workflows tailored to specific challenges. Using recent practical examples, we’ll demonstrate how these integrations can simplify complex tasks, save time and enhance data quality.
Coordinated Disclosure for ML - What's Different and What's the Same.pdf
Coordinated Disclosure for ML - What's Different and What's the Same.pdfPriyanka Aash Coordinated Disclosure for ML - What's Different and What's the Same
EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdf
EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdfEarley Information Science As AI reshapes expectations in retail and B2B commerce, organizations are recognizing a critical reality: meaningful AI outcomes depend on well-structured, adaptable infrastructure. In this session, Seth Earley is joined by Phil Ryan - AI strategist, search technologist, and founder of Glass Leopard Technologies - for a candid conversation on what it truly means to engineer systems for scale, agility, and intelligence.
Phil draws on more than two decades of experience leading search and AI initiatives for enterprise organizations. Together, he and Seth explore the challenges businesses face when legacy architectures limit personalization, agility, and real-time decisioning - and what needs to change to support agentic technologies and next-best-action capabilities.
Key themes from the webinar include:
Composability as a prerequisite for AI - Why modular, loosely coupled systems are essential for adapting to rapid innovation and evolving business needs
Search and relevance as foundational to AI - How techniques honed-in enterprise search have laid the groundwork for more responsive and intelligent customer experiences
From MDM and CDP to agentic systems - How data platforms are evolving to support richer customer context and dynamic orchestration
Engineering for business alignment - Why successful AI programs require architectural decisions grounded in measurable outcomes
The conversation is practical and forward-looking, connecting deep technical understanding with real-world business needs. Whether you’re modernizing your commerce stack or exploring how AI can enhance product discovery, personalization, or customer journeys, this session provides a clear-eyed view of the capabilities, constraints, and priorities that matter most.
Curietech AI in action - Accelerate MuleSoft development
Curietech AI in action - Accelerate MuleSoft developmentshyamraj55 CurieTech AI in Action – Accelerate MuleSoft Development
Overview:
This presentation demonstrates how CurieTech AI’s purpose-built agents empower MuleSoft developers to create integration workflows faster, more accurately, and with less manual effort
linkedin.com
+12
curietech.ai
+12
meetups.mulesoft.com
+12
.
Key Highlights:
Dedicated AI agents for every stage: Coding, Testing (MUnit), Documentation, Code Review, and Migration
curietech.ai
+7
curietech.ai
+7
medium.com
+7
DataWeave automation: Generate mappings from tables or samples—95%+ complete within minutes
linkedin.com
+7
curietech.ai
+7
medium.com
+7
Integration flow generation: Auto-create Mule flows based on specifications—speeds up boilerplate development
curietech.ai
+1
medium.com
+1
Efficient code reviews: Gain intelligent feedback on flows, patterns, and error handling
youtube.com
+8
curietech.ai
+8
curietech.ai
+8
Test & documentation automation: Auto-generate MUnit test cases, sample data, and detailed docs from code
curietech.ai
+5
curietech.ai
+5
medium.com
+5
Why Now?
Achieve 10× productivity gains, slashing development time from hours to minutes
curietech.ai
+3
curietech.ai
+3
medium.com
+3
Maintain high accuracy with code quality matching or exceeding manual efforts
curietech.ai
+2
curietech.ai
+2
curietech.ai
+2
Ideal for developers, architects, and teams wanting to scale MuleSoft projects with AI efficiency
Conclusion:
CurieTech AI transforms MuleSoft development into an AI-accelerated workflow—letting you focus on innovation, not repetition.
PyCon SG 25 - Firecracker Made Easy with Python.pdf
PyCon SG 25 - Firecracker Made Easy with Python.pdfMuhammad Yuga Nugraha Explore the ease of managing Firecracker microVM with the firecracker-python. In this session, I will introduce the basics of Firecracker microVM and demonstrate how this custom SDK facilitates microVM operations easily. We will delve into the design and development process behind the SDK, providing a behind-the-scenes look at its creation and features. While traditional Firecracker SDKs were primarily available in Go, this module brings a simplicity of Python to the table.
AI vs Human Writing: Can You Tell the Difference?
AI vs Human Writing: Can You Tell the Difference?Shashi Sathyanarayana, Ph.D This slide illustrates a side-by-side comparison between human-written, AI-written, and ambiguous content. It highlights subtle cues that help readers assess authenticity, raising essential questions about the future of communication, trust, and thought leadership in the age of generative AI.
Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO Alliance Securing Account Lifecycles in the Age of Deepfakes
CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025
CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025pcprocore 👉𝗡𝗼𝘁𝗲:𝗖𝗼𝗽𝘆 𝗹𝗶𝗻𝗸 & 𝗽𝗮𝘀𝘁𝗲 𝗶𝗻𝘁𝗼 𝗚𝗼𝗼𝗴𝗹𝗲 𝗻𝗲𝘄 𝘁𝗮𝗯> https://pcprocore.com/ 👈◀
CapCut Pro Crack is a powerful tool that has taken the digital world by storm, offering users a fully unlocked experience that unleashes their creativity. With its user-friendly interface and advanced features, it’s no wonder why aspiring videographers are turning to this software for their projects.
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...
Wenn alles versagt - IBM Tape schützt, was zählt! Und besonders mit dem neust...Josef Weingand IBM LTO10
Quantum AI: Where Impossible Becomes Probable
Quantum AI: Where Impossible Becomes ProbableSaikat Basu Imagine combining the "brains" of Artificial Intelligence (AI) with the "super muscles" of Quantum Computing. That's Quantum AI!
It's a new field that uses the mind-bending rules of quantum physics to make AI even more powerful.
9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe Software This session will cover a common use case for local and state/provincial governments who create and/or maintain their 9-1-1 addressing data, particularly address points and road centerlines. In this session, you'll learn how FME has helped Shelby County 9-1-1 (TN) automate the 9-1-1 addressing process; including automatically assigning attributes from disparate sources, on-the-fly QAQC of said data, and reporting. The FME logic that this presentation will cover includes: Table joins using attributes and geometry, Looping in custom transformers, Working with lists and Change detection.
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdf
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdfPriyanka Aash A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...
“MPU+: A Transformative Solution for Next-Gen AI at the Edge,” a Presentation...Edge AI and Vision Alliance
Ad
Chrome release cycle
- 1. Chrome Release Cycle Author: Anthony Laforge ([email protected])
- 2. Our Philosophy • Think of any major website, even the fancy Web 2.HTML5 ones... do they have version numbers? • We took the same approach to our client software as an online web service. • That is... we treat releases as a means of getting features out to users and not goals in and of themselves. • It's about flow.
- 3. How Our Users Work • Users sign up for Chrome release channels based on the level of stability they want. • Updates happen automatically in the background. • New features and functionality just flow in without any effort on the user's part.
- 4. How the Chrome Team Works • Developers work almost exclusively on a single central trunk (possible due to our try bots and continuous build infrastructure) • Our branches stem from points on the trunk • We stabilize branches by pulling in changes from trunk (i.e. everything lands on trunk first)
- 5. Where we started (v1-4) - On Paper
- 6. In practice, for that final beta...we'd • Cut a branch (when we thought we had everything) • Merge about ~500 patches (since we didn't have everything) • Spend weeks stabilizing and re-stabilizing issues. • Ended up working 1-3 months to get a release out the door, always certainly missing our 13 week plan. • And at the end finally shipping something we were happy with... but that left us pretty drained (i.e. the bad flow)
- 7. The chain of events • We'd hold releases, sometimes our branch points, until features were done, which meant... • Lots of changes got queued up on the trunk, which caused... • Engineers merging lots of changes to the branch, which led to... • Instability on the branch that we had to deal with and that meant...
- 8. That chain of events... • Long lived branches, which... • Made supporting the branch (i.e. merging changes) more difficult as we drifted further from the trunk... • All of which led to... o Unpredictable release cycles, with date targets we could never hit, and.... o Engineers who were always in a rush to get their features into "this" release since we couldn't make any promises about the schedule
- 9. Which led me to think... • I need a long vacation. • There has to be a better way. • What's causing things not to flow smoothly? ...Yes...In that order.
- 10. Primary Goals • Shorten the release cycle and reduce the life span of a branch (make merges easier) • Make releases more predictable and easier to scope • Reduce the strain on the entire team Good Bad
- 11. Goal to Plan - Getting down the cycle • Originally set out a plan to simplify the 12 week cycle, 6 weeks on dev, 6 weeks on beta, and then to stable. • Once diagrammed, using blocks to represent the weeks, realized that with 3 channels you could have two overlapping releases running at once, which could get us a stable release ~ every 6 weeks.
- 12. Block diagrams
- 13. It was a start, but it wasn't the full answer • Sure, turning the wheel faster would make some things, like merges, easier. • But without addressing the scope problems, the flow wouldn't be any better and would continue to interrupt releases. • Things wouldn't be any more predictable and the whole cycle would just fall apart (more puddles, less of a stream).
- 14. Goal to Plan - Controlling Scope • The pace of the schedule sets the boundaries for the amount of work that can be completed. • It's important to have specific points in the schedule to review features and cut scope. • Establish clear expectations (and engineering practice) to developers that any features not ready to ship at branch will be disabled (i.e. we only cut post branch, never add).
- 15. Plan to Pitch • Reached out to the various cross functional groups on the Chrome team, who would all be impacted, before approaching our executives. o Engineering, QA, Product, Marketing, Support, Localization, Security, etc... • There were a lot of concerns to address, but the exercise forced a lot of thought on the implications of the schedule change. • It took time, but it made the pitch easier to present to the leadership and the rest of the team.
- 16. Concerns • Would large feature development still be possible? "Yes, engineers would have to work behind flags, however they can work for as many releases as they need to and can remove the flag when they are done." • Can the engineers keep up? "Their pace won't need to change, since features can be disabled there should be no milestone pressure, things ship when they are ready." • What would a world look like where we didn't base our marketing on releases? "We market features, not releases."
- 17. And so we implemented it 11 week overlapping schedules.
- 18. Our General Rules • The branch point is the end of our development cycle • Features only get disabled post branch point • Features should be engineered so that they can be disabled easily (1 patch) • Only stability, security, and critical regressions can ever block a release
- 19. Things we struggled with • Overcoming team inertia (particularly when we cut scope) • Saying no consistently to the team • Fighting the urge to return to date driven management decisions • We initially didn't solve the trunk->dev->branch time to patch problem (daily channel helped). • Setting the right burn down point (i.e. branch point). • Disabling features.
- 20. Key Lessons • Having clear and concise rules is important. • Predictable schedules cut down on communication costs and team confusion. • It takes work and fore-thought to disable features. • Diligent feature tracking is important.
- 21. Conclusion • Speed alone isn't always the right answer, it's about keeping things running smoothly. • For us, scope was getting in the way of that goal. We basically wanted to operate more like trains leaving Grand Central Station (regularly scheduled and always on time), and less like taxis leaving the Bronx (ad hoc and unpredictable).