2009/1/4 Rajko M. <rmatov101@charter.net>:
On Saturday 03 January 2009 05:34:31 pm Eric Springer wrote:
On Sun, Jan 4, 2009 at 7:06 AM, Rajko M. wrote:
Situations where something doesn't work are common when you try to synchronize few thousands software titles. Some configurations will work, some will fail.
This is true, but now how to home in on the problem source, so a solution is found efficiently? Do you? a) Update and change absolutely everything, and release probably as one huge pile of broken stuff, which then needs a lot of sorting through? b) Phased updates, some parts release stable as others change, with only minimal required bug fixes going in to the rest of the system? c) Many small steps, rolling back 'bad' changes, with one release rolling on and evolving into the next? Some method of moving forwards, and rolling back changes; appears to me the best shot at growing tester base, and maintaining sufficient quality for the code to run on real hardware, not virtualised. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org