Comments for Continuous Delivery

Comment on Make Large Scale Changes Incrementally with Branch By Abstraction by [转载]什么是重构，什么不是重构 | EmLinux

[转载]什么是重构，什么不是重构 | EmLinux — Mon, 14 May 2012 04:50:05 +0000

[...] “大规模重构”会变的很糟糕。你可能需要花数周、数月(甚至数年)才能完成，需要你对软件的很多部分进行改动。软件会因此不能运行，需要分多次发布这些变更，需要你做临时的台架(scaffolding)和变通方案——尤其是你采用短周期的敏捷开发方法时。这时Branch by Abstraction这样的实践方法就派上用场了，它能帮你在长周期内管理代码中的变化。 [...]

Comment on Make Large Scale Changes Incrementally with Branch By Abstraction by 什么是重构，什么不是重构 - 博客 - 伯乐在线

什么是重构，什么不是重构 - 博客 - 伯乐在线 — Mon, 14 May 2012 02:10:09 +0000

Comment on On DVCS, continuous integration, and feature branches by Jez Humble

Jez Humble — Wed, 09 May 2012 23:36:00 +0000

> I tend to agree with them, since the software is often not in good condition.
This is the root cause of the problem. And of course your customers are responding rationally.

Over time, you need to move to a mainline development model, and require customers to upgrade in order to receive support. But for them to do that, you must first ensure that you fix the quality problems in mainline. Management has to ensure adequate resources are available to achieve this goal.

Once this is done, you can move most of your customers onto the mainline version, requiring them to do so in order to receive support. You’ll probably have to keep some customers on older versions – but management will need to be courageous about who they allow to stay on old versions, and ensure they are always working to minimize the number of different versions being supported, with a goal of eventually moving everyone onto the mainline version.

One absolute rule has to be that features never get backported to older versions. Hopefully, if you continue to deliver valuable features, this will act as a “carrot” to convince people to upgrade.

HP had a similar problem with their firmware – you can read about how they moved to a mainline model in this book: http://www.amazon.com/dp/0321821726/

Comment on Organize software delivery around outcomes, not roles: continuous delivery and cross-functional teams by Team, Player and Game Dimensions « Slog Maverick

Team, Player and Game Dimensions « Slog Maverick — Wed, 09 May 2012 15:18:02 +0000

[...] about let’s forget all that and just get something shipped today, sound [...]

Comment on About by Facebook and the perpetual beta | Amanda Belton

Facebook and the perpetual beta | Amanda Belton — Mon, 30 Apr 2012 08:36:38 +0000

[...] in a Project Runway type of reality show – maybe next year we’ll be cool and hip? Could Jez Humble be a fabulous Tim Gunn type of mentor telling pairs to ‘make it work’? Share [...]

Comment on Continuous Delivery: The Value Proposition by Design and analysis occur at all points in the software lifecycle | Mike Long

Mon, 30 Apr 2012 02:59:06 +0000

[...] In software development, the need to continuously deliver working software increases as companies engage customers in new and innovative ways. The organization must prioritize this capability as a core value in order to learn about customers and iterate rapidly. Sometimes we need to change direction in a more radical way if we discover what we’ve built isn’t valuable.[5] [...]

Comment on Continuous Delivery: The Value Proposition by Design and analysis occur at all points in the product lifecycle « Mike Long

Sun, 29 Apr 2012 05:20:58 +0000

Comment on Continuous Delivery and ITIL: Change Management by Continuous Delivery and ITIL: Change Management | ITIL Training Zone Blog from the Online ITIL Experts

Fri, 27 Apr 2012 09:10:29 +0000

[...] View original article… /* [...]

Comment on Make Large Scale Changes Incrementally with Branch By Abstraction by What Refactoring Is and What It Isn’t | Prasun’s Techblog

What Refactoring Is and What It Isn’t | Prasun’s Techblog — Sat, 21 Apr 2012 19:12:54 +0000

[...] like Branch by Abstraction (original entry of this technique) come in to play for these refactorings, to help you manage [...]

Comment on Continuous Delivery vs Continuous Deployment by Import Continuous Delivery – Part 1: Agile Processes taken to the Next Level | zeroturnaround.com

Tue, 17 Apr 2012 14:51:27 +0000

[...] Over the last year or two, organizations with strong development teams have undergone something of a revolution. It really began in 2001 with the Agile Manifesto signalling the end of the waterfall methodology in software development, in favor of Agile tools and processes. These tools (Scrums, sprints, etc) have set the stage for what is turning out to be the ‘third renaissance’ in software development. “DevOps” – the merging of Development and Operations – viewing the entire delivery cycle of software as a single process, rather than the walled silos of old – is the stage for this new approach to application deployment: Continuous Delivery. (Read up for more understanding of Continuous Delivery vs. Continuous Deployment) [...]