Comment #13 on issue 8695 by cbruscato: Download troubles http://code.google.com/p/chromium/issues/detail?id=8695
Don't take this the wrong way but I feel I need to summarize the state of feelings in alot of testers right now. We are here to support you. We download the latest builds and report bugs to you so that the team can build a better product. The typical mantra amongst programming teams, is not to check-in broken code. It just feels wrong that required functionality was removed from the project, not from nightlies, but from dev-channel release builds; in the hopes that it would be added back in. Now correct me if I am wrong but this type of regression caused by new feature implementation should result in a Branch build, should it not? So that this code isn't checked into the Trunk build until it is complete and ready for testing. In the future can we start a branch\trunk build process, so that we don't end up testing things in-progress. It seems like this could eventually lead to completely broken builds being distributed to the dev channel. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
