Re: integration and master divergence
Maik Musall <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.wonder-disc |
|---|---|
| Message-ID | <[email protected]> |
Hi Kieran, Am 17.07.2012 um 19:22 schrieb Kieran Kelleher: > The original plan with integration was that commits that survived for at least a month in integration without > breakage or bugs would be deemed worthy of merging to master. > If all goes well, this merge will be shifted to master and then we can from then on ONLY merge integration commits that are a month old PERIODICALLY (1-4 weeks intervals). As I see it, master should be a stable thing that production apps can rely on. That requires two premises: 1. An integration test of the periodic merge to make sure everything works fine with everything else after merging stuff that nobody was running in exactly that combination before. 2. Some sort of version number to tag each release, so that it will be possible for everyone who experiences problems in production can easily switch back to the previous master release. Every other framework out there has version numbers that make it possible to refer to a specific release. What do you think? Maik ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/