On Tue, Mar 5, 2013 at 8:13 PM, Scott Kitterman <ubu...@kitterman.com> wrote: > I agree. My main point is that such things are pre-requisites to a new > release model. We don't have them, so we should get them before we change to > something we're not ready to support.
My feeling here is that new processes and models need to have a level of assurance that it is going to work. I am not averse to taking risks, but there needs to be (a) a reasonable amount of reward to justify the risks, and (b) enough assurance to ensure that the change is not reckless. Of course the challenge in a community such as ours is that we all have different definitions of risk and assurance - I think the trick in this discussion is finding a good middle ground of what is considered acceptable risk and requisite assurances. Jono -- Jono Bacon Ubuntu Community Manager www.ubuntu.com / www.jonobacon.org www.identi.ca/jonobacon www.twitter.com/jonobacon -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
