There are techniques to do that, stuff like feature toggle for instance. The Agile Executive just ran a story on this recently.
________________________________ Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -----Original Message----- From: Thiessen, Todd (Todd) [mailto:tthies...@avaya.com] Sent: Monday, November 08, 2010 11:52 AM To: Maven Users List Subject: RE: Continuous Delivery and Maven > In my view of CD, you wouldn't come back, ever. You'd just commit code > that triggers a build and if it passes each and every quality gate > along the way it would get deployed. I am even struggling with that. A commit of some code, does not imply a deliverable feature. You may use any number of commits to complete a particular user story. I don't see how delivering an in progress story has any value. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
